Glossary · Docs · RowCall

Term	Meaning
Action	Something a call asks your systems to do or look up while the shopper is on the line, such as "update delivery address". See Actions.
Allowed actions	The actions a flow may use. Anything else is refused.
Answer	A typed value a call captures, such as `yes`, a date or an address. The shopper's own words stay in the call's transcript.
Answer rate	The share of calls the shopper picked up.
API key	A secret that lets your systems use the RowCall API. Test and live keys are separate.
Audit log	The record of who changed what in an org, and when.
Call record	Everything about one call: status, recording, transcript, answers, actions, outcome.
Call type	Transactional or service, under India's TRAI rules. Decides the consent a call needs.
Calling hours	The days and times your org allows calls, in the shopper's time zone.
Consent record	Proof that a shopper agreed to a kind of call: the wording, when and where.
Credits	Prepaid balance that calls and the AI they use draw down.
Disclosure line	The opening sentence of every call, saying it is an automated assistant calling for your store.
Draft	A version of a flow being edited. Calls never run drafts.
Flow	A reusable call: steps, inputs, answers, outcomes and allowed actions.
Flow library	Ready-made ecommerce flows you can copy into your org.
Handoff	A person from your team taking over a live call (`transfer`), or the assistant telling the shopper the team will call back (`callback`), as your SOP says.
Idempotency key	A unique key sent with an API request so a retry never starts the same call twice.
Input	A typed detail sent with each run, such as the order number or the shopper's phone.
Listen in	Joining a live call silently from the browser.
Member	A person in an org, with one role.
Opt-out	A shopper's request not to be called again. Applies to every flow in the org.
Org	Your company's workspace in RowCall. Flows, calls and results belong to it.
Outcome	How a run ended, such as `confirmed` or `needs_team`.
Partial	A call that ended before all answers were captured. What was captured is kept.
Partner	A commerce platform, such as Glood, that offers RowCall flows to its merchants.
Pending action	An action your system is still working on; it finishes later and the call or follow-up continues.
Playbook	A docs page for one ecommerce use case: when to call, the flow, what to measure.
Preview	A feature that is designed and documented but not live yet.
Promotional call	A call that offers something, such as a discount. Not available on RowCall.
Publish	Making a flow version live for new calls.
Results	The table of runs for a flow, one row per call and one column per answer.
Role	What a member may do: Owner, Admin, Builder, Operator or Viewer.
Run	One use of a flow for one shopper. A run places a call.
Service call	A call that helps an ongoing purchase or order. Needs explicit consent, valid 7 days.
Simulation	A test call in your browser using your microphone. Nothing is dialled.
SOP	Plain-language instructions for everything off a flow's path: what the assistant may say, how it answers other questions, and when it hands over. Set for the org in Settings → SOP; each flow can add to or replace parts.
Step	One part of a flow's script, such as "confirm the address".
Test mode	Running flows with test API keys: nothing is dialled, the flow is walked through with given answers, and events and actions go to your test endpoints.
Transactional call	A call about a transaction the shopper just started, within 30 minutes.
Version	A published, numbered snapshot of a flow. Each call records the version it used.
Webhook	A signed message RowCall sends to your system when something happens, such as `run.completed`.

Next stepBack to the docs home

Pick up the journey where you left off.

Search the docs