Now inviting stores. Join the waitlist to hear the agent call you.
Join the waitlistSecurity and trust
These rules are built into the product, not settings you have to remember. When a rule can’t be met, the call isn’t placed.
In India, in Bengaluru.
Call records, recordings and transcripts are stored in India (Bengaluru), close to the shoppers we call. Every connection uses TLS, and stored data, recordings included, is encrypted at rest. Your shoppers’ data is used only to run your calls; export everything at any time, and we delete on request.
Only your team, by role.
Owners, admins, builders, operators and viewers see only what their role allows, and the server checks every request. An audit log records who changed a setting, a role or a flow, and when. Webhooks and action requests are signed, so your systems can verify they came from RowCall.
No consent, no call. One “no” stops them all.
Each flow has a call type. A call needs a consent record or an ongoing transaction, goes out only inside calling hours, and an opt-out covers every flow at once. When a rule can’t be met, the call isn’t placed and the reason is shown.
Ask your questions, take your allowed actions. Nothing else.
Every call says it’s automated in the first sentence, in the shopper’s language. The flow is fixed: the caller asks your questions and only those, and can take only the actions you allowed. It never asks for card numbers, codes, OTPs or passwords; payment always happens through a secure link.
Follow the data
An order or checkout needs a call. Your store (or an app such as Glood) asks RowCall to start one.
The detail
Open by invitation
Join the waitlist and we’ll invite you to try the agent with free test calls. No card needed.
Join the waitlist
