Built-in CRM

A CRM your AI phone agent reads and updates during the call

Design the records you keep, or start from a template or a spreadsheet. Your AI voice agents find callers by phone number, add new records and change details while they talk, inside the rules you set.

  • Six templates, or start from a file
  • Encrypted fields, AES-256-GCM
  • API keys and signed webhooks
Objects & fields

Design the CRM around how you work

An object is a kind of record you keep, like contacts, companies or deals. Fields are the details you store on each record. Build them yourself, or start from a template and change anything later.

  • Six templates: Sales CRM, Support desk, Clinic & patients, Real estate, Orders & delivery and a simple contact list
  • Fields for text, numbers, money, dates, phone numbers, emails, choices, ratings and links between records
  • Table and board views, filters, saved views and a trash you can restore from
Start from a file

Already keep a spreadsheet? Build the CRM from it.

Drop a CSV or Excel file and AutoVator suggests a field for each column. You only check the columns, then build.

  1. Upload

    CSV or Excel (.xlsx, .xls, .ods), up to 10 MB and 20,000 rows, with or without a header row. The first sheet is used.

  2. Check the columns

    Types are found for you. Untick a column to leave it out, rename fields, pick the title, and mark fields encrypted or searchable.

  3. Build

    The records are imported into a new object, private by default. Build a ready dashboard for them in the same step.

  4. Connect

    Open the records, edit the fields, or connect the object to an AI agent so it can use them on calls.

For your AI agents

Your AI agent works in the CRM while it talks

Create a tool for an object, choose what the agent may do and which fields it may read or change, then select the tool on your agent. Three steps, about two minutes.

  • Finds the caller by phone numberWith no number given, the agent looks up the number the person is calling from.
  • Privacy optionsCallers only see their own record, and the agent can ask for the phone number before a change or a delete.
  • Answers made to be spokenMissing details, several matches or a forbidden action come back as plain guidance, so a call never breaks.
A real call

“I moved, can you update my address?”

The agent finds the caller from the number they call from, asks only for what is missing, and saves it. The change appears in the activity log, marked as made by your AI agent.

  1. CallerHi, I just moved. Can you update my address?
  2. Contacts · find by the caller’s number → Jane Cooper, Boston
  3. AI agentOf course, Jane. What is your new address?
  4. Caller12 Oak Street, Austin.
  5. Contacts · update Jane Cooper → city, address saved
  6. AI agentDone. Your address is now 12 Oak Street, Austin. Anything else I can help with?
Dashboards & reports

See what is happening, as it happens

Build dashboards from widgets, or start from a template: Overview, Sales pipeline, AI agents or Support desk. Figures refresh by themselves every 10 seconds.

  • Figures, goals, trends, bars, donuts, funnels, tables, live activity and AI activity
  • A report builder: count, sum, average, lowest or highest, grouped by any field, with filters and a comparison with the previous period
  • Saved reports, shown as bars, lines, areas, donuts or tables, and exported to CSV
  • An AI agent report: what your agents looked up and changed, and how often it worked
Protection

Private by default, encrypted where it matters

Customer records hold personal details. The CRM keeps every account apart and encrypts the fields you choose, without making them harder for your agent to use.

Your own key

Each account has its own random data key, itself protected by the master key of the server.

Encrypted fields

Fields you mark as encrypted are stored with AES-256-GCM. Templates encrypt contact details and notes by default.

Still easy to find

Exact lookups on encrypted fields use a keyed hash, so your AI agent can still find a caller by phone number.

Kept apart

Every account has its own CRM space and every request is limited to it. Record ids in links are random.

Kept out of history

Values of encrypted fields never appear in the activity log.

Password for sensitive actions

Exports, deletions for good, and new API keys or webhooks ask for your password again.

API & webhooks

Keep your other systems in step

Give another app its own key to read or write records, and push every change to it as it happens.

  • API keys with permissions (read, write, delete, schema), a choice of objects, an IP allow-list and an expiry date
  • Endpoints to list, read, create, update, delete and upsert records
  • Webhooks for created, updated and deleted records, signed with HMAC-SHA256 and sent only to https addresses
  • Failed deliveries are retried up to 5 times, and the delivery log shows every try
Your team

Sub-accounts share one CRM

Sub-accounts work in the CRM of their main account, so everyone sees the same customers. The main account keeps the keys.

WhatMain accountSub-accounts
Records, views and the boardYesYes, in the same CRM
Dashboards and reportsYesYes
Import and exportYesNo
AI agent toolsYesNo
API keys and webhooksYesNo
Settings, deleting objects or fieldsYesNo
FAQ

CRM questions

Still unsure about something? Ask us directly

Can my AI phone agent use the CRM during a call?

Yes. In CRM → AI agents you create a tool for an object, such as Contacts, choose what the agent may do (find, add, change or delete a record) and which fields it may read or change. Then you select the tool in the Connections step of your AI agent, and the lines the agent needs are added to its instructions automatically.

Do I have to build the CRM from scratch?

No. Start from one of six templates (Sales CRM, Support desk, Clinic & patients, Real estate, Orders & delivery or a simple contact list), with a few sample records if you like. Or upload a CSV or Excel file: AutoVator suggests a type for each column and builds the object for you.

How is my CRM data protected?

Every account has its own CRM space, and every request is limited to it. Each account also has its own random data key. Fields you mark as encrypted are stored with AES-256-GCM, and the templates encrypt contact details and notes by default. Values of encrypted fields never appear in the activity log.

Can the AI agent still find a caller when the phone number is encrypted?

Yes. Exact lookups on encrypted fields use a keyed hash, so the agent can find a record by phone number or email. Encrypted fields can be shown, edited, exported and read by the agent, but they cannot be sorted, grouped, charted or searched with “contains”.

Can I connect the CRM to another app?

Yes. Create an API key with the permissions, objects and IP addresses it may use, and an expiry date if you want one. Webhooks send created, updated and deleted records to another app over https, signed with HMAC-SHA256. A delivery that fails is retried, and a webhook pauses after 20 failures in a row.

Do sub-accounts get their own CRM?

Sub-accounts work in the CRM of their main account: the same records, views, dashboards and reports. Only the main account manages API keys, webhooks, AI agent tools, settings, imports and exports.

I already use HubSpot. Do I need this CRM?

Not necessarily. Your AI agent can also work with HubSpot CRM, Google Sheets, Airtable and other apps through integrations. The built-in CRM is there when you want your records in the same account as your calls, without another subscription to connect.

Can I export my data?

Yes. The main account can export any object to a CSV file that opens in Excel, Numbers or Google Sheets. Encrypted fields are decrypted in the file, so AutoVator asks for your password again before the download.

Give your AI agent a memory

Create a free account, start from a template or a spreadsheet, and connect your records to an AI agent in a few minutes.