Skip to main content
Recepta.ai is one system with several surfaces. Understanding six objects makes the rest of the docs straightforward.

​
The object model

Your company account. It owns everything below: users, agents, phone numbers, contacts, billing, and integrations. Data never crosses workspace boundaries — every API request and every agent action is scoped to yours.
An optional subdivision of a workspace, for businesses running more than one branch, franchise, or service area. Locations can have their own phone numbers, hours, calendars, and agents while sharing billing and team.In the API, pass the x-location-id header to scope a request to one location. See Locations.
The AI that actually talks to people. An agent bundles a voice, a personality, the business knowledge it can draw on, the questions it asks each caller type, and the actions it’s allowed to take — booking, transferring, texting.Most workspaces run one agent. You’d add more when a location, a language, or a campaign needs genuinely different behavior. See AI agents.
What the agent knows: your business profile, services, pricing, policies, and FAQs. Knowledge is workspace-level, so every channel answers consistently — the chat widget and the phone agent give the same quote. See Knowledge base.
A person Recepta.ai knows about. Contacts arrive from calls, CSV import, web forms, Facebook lead ads, your CRM, or the API, and carry the tag source recording where they came from. Contacts are what outbound campaigns and sequences run against. See Contacts.
Every interaction produces a record: calls with duration, transcript, recording, and outcome; SMS and chat as threaded conversations. These are what you review, what analytics aggregate, and what webhooks fire on. See Call logs.

​
How a call flows

1

The call arrives

Someone dials one of your Recepta.ai numbers, or your existing line forwards to it. The agent assigned to that number picks up.
2

The agent identifies the caller

It works out which of the four caller types it’s dealing with — potential customer, existing customer, sales call, or other — and follows the script you configured for that type. If a CRM is connected, an existing customer can be recognized from their number.
3

It does the job

Answers questions from your knowledge base, collects the details you asked for, checks real calendar availability, and books. If your rules say a human should take this one, it transfers.
4

Everything is written down

A contact is created or updated, the appointment lands on your calendar and in your CRM, confirmations and reminders are queued, and the call record — transcript, recording, outcome — appears in your dashboard.
5

Downstream systems hear about it

Subscribed webhooks fire, and usage is metered against your plan.

​
Inbound and outbound

The same agents and knowledge power both directions.

Inbound

Calls, texts, chats, and form submissions coming to you. This is the receptionist — always on, never a voicemail.

Outbound

Campaigns and sequences reaching out to contacts across call, SMS, email, and voicemail drop. This is the growth engine. See Outbound.

​
Where you’ll work