Skip to main content
Most questions are answered faster by looking in the right place than by waiting on a reply. Here’s the order worth trying.

​
Check these first

The agent said something wrong

Read the transcript. Wrong facts are almost always a gap in your knowledge base or business profile, not a fault in the agent.

Texts aren't sending

Nearly always A2P 10DLC registration still pending or rejected. Voice works before A2P is approved; SMS doesn’t.

Bookings aren't reaching my calendar

Check the integration’s last sync time, and confirm you have exactly one source of availability connected.

An API call is failing

The status code tells you which of the four usual causes it is — auth, permission scope, malformed field, or rate limit.

​
Contact us

Email info@recepta.ai. To get a useful answer on the first reply rather than the third, include:
1

Your workspace name

We can’t look anything up without it.
2

What you expected, and what happened

Both halves. “The agent didn’t book” is a symptom; “I asked for Thursday morning and it offered next week” is something we can trace.
3

A specific example

A call ID, a phone number and rough time, a contact, or the exact request and response for an API problem. One concrete case beats a general description.
4

When it started

And whether anything changed around then — a plan change, a new integration, an edit to your agent.
Never send us an API key, a password, or a customer’s card details. If you think a key has been exposed, revoke it from API keys first, then tell us. See Authentication.

​
Something urgent

If calls aren’t being answered at all, check first whether your number still forwards to Recepta.ai and whether your subscription is current — a failed payment eventually suspends service. See Phone numbers and Billing. Then email us with urgent in the subject and your workspace name.

​
Security

Report a suspected vulnerability to info@recepta.ai with reproduction steps. Please don’t test against other customers’ workspaces or use live customer data. See Security & privacy.