What you need first
The CRM is the system of record for your business. It starts from the people your agent talks to and grows into everything you keep about them: companies and customers, your own kinds of record (treatments, properties, contracts) with links, calculated fields and status lifecycles, meetings, tasks, rules that act on their own, roles, dashboards, and connections to your other tools. This guide is the hands-on part; for how it fits with your other apps, read CRM: what it does.
- People and businesses: contacts (filled by your agent, imports or by hand), companies, and customers — a company is a prospect, customer, partner or reseller.
- Your own model: record types with fields, links between them, rollups, formulas, statuses with allowed moves, and pages you design.
- Work: tasks, meetings, an activity timeline per person, rules, roles and dashboards.
- Connected: to your agent and its conversations, to Sales leads and Booking, to broadcasts, to Claude or ChatGPT, and out to other systems through webhooks and a developer API.
- A workspace with the CRM switched on. Access is per workspace, not per person. Without it, signing in lands you on a request-access screen.
- An agent in the same workspace. The CRM has no contacts of its own to start with; it reads them from the agent you connect. No agent yet? Create one in the Agents app first.
- Workspace admin rights. Connecting the agent, designing pages, roles and rules are admin actions. A member sees them but cannot change them.
Pick how you want to work. The choice below follows you down the whole page.
- In Claude open Customize → Plugins → Discover, search AssistantLabs and click Add.
- In a new chat type the command below. It starts the sign-in; the CRM comes with the plugin.
/allist_record_types and tells you what it found.Using ChatGPT? Same tools, same prompts — connect it with Connect ChatGPT. Note that on a Plus or Pro account a custom connector is read-only, so the prompts that build or change things need a Business, Enterprise or Edu workspace.
- Open crm.assistantlabs.io, or pick CRM in the app switcher, and sign in with your AssistantLabs account.
- If you land on the request-access screen, the CRM is not on for this workspace yet. Signed in, you get your identity card and a one-click request.
- Once you are in, the navbar is your map. Left to right it runs Home, Contacts, Companies, Customers, your own record types, Tasks, Dashboard, Automations and Settings.
Your first 10 minutes
Two things make the CRM yours: it reads the contacts of your agent, and it knows the things your business keeps that are not people — treatments, properties, contracts.
1. Connect your agent
list_crm_contacts.- On Home you see Connect your agent. Click Connect.
- That opens Settings → Connections. Under Connect, open Select an agent… and pick your agent.
- Click Connect. The card turns to Connected.
- Choose what comes in: all contacts and conversations, or only those with the labels or sources you pick. You can change the choice later.
Open Contacts: everyone the agent has spoken to — on WhatsApp, Instagram, email or the web — is already there. The CRM only reads your conversations; it never edits or deletes them.
2. Create your first record type
People, companies and customers already exist — do not make a record type for them. A record type is a thing the business keeps: a treatment, a property, a contract, a unit with a serial number.
list_record_types, describe_crm_field_types, create_record_type, set_crm_navbar, set_crm_currency. It creates the type with its fields in one go and puts it in the bar.Now make it readable. Statuses get colours, and the type gets an icon:
upsert_record_field (status colours), describe_page_blocks (the icons and colours it may use), set_page_design with the type’s appearance.You have two ways in. Let the CRM propose a design from what your agent already knows about the business, or define one type yourself.
- Click Settings, then Record design in the left list.
- Click Design my CRM. It reads your connected agent, works out what kind of business this is, and proposes pages for Contacts, Companies and Customers.
- Review the highlighted additions. Keep what fits, remove the rest with the ✕, and press Publish. Nothing is saved until you publish.
For a thing that is not a contact, a company or a customer, click the dashed New record type card instead. It is a page, not a pop-up, because it is done once.
You land straight in the designer for the new type. Add fields with + New field: Text, Long text, Number, Money, Date, URL, Single choice or Multiple choice. For a choice, write the options one per line.
Currency, once: In Settings → Overview, the Currency card sets what every money field shows across the CRM. Leave it on automatic and it follows your agent.
Bring in what you already have
The people your agent talked to are already in. Import is for everyone else: an old spreadsheet, your phone book, a list from another system.
People
upsert_crm_contact once per person, then list_crm_contacts.- Open Contacts and click Import above the list.
- Choose A spreadsheet (a CSV from Excel or Google Sheets) or Your phone contacts (a .vcf file).
- A spreadsheet: drop the file, then tell it what each column holds. The ones it recognised are already filled in; a column you leave unmatched is kept as an extra field on the contact.
- Under If someone is already on your list pick Fill in what is missing: it adds the email, tags and fields they lack and never overwrites what is there.
- Check the preview, then press Import. Nothing is saved before that.
From a phone: On an iPhone: Contacts → select → Share. On Android: Contacts → Settings → Export. Then choose the .vcf file.
Records of your own type
suggest_crm_import_mapping (columns → fields), then import_crm_records — a dry run by default: every row is checked and nothing is written. After your OK it runs again for real.- Open the tab of your type (for example Treatments) and click Import.
- Drop an Excel or CSV file with the column names in the first row.
- Choose the field each column goes into, and what to do with each row: Add new, Add or update or Update only.
- Press Check the file. Rows with problems are listed and skipped; nothing has been saved yet. Then import the valid rows.
Companies, customers, meetings and the timeline
People are one half of a business relationship. The other half is the company they belong to, whether it is a customer, what was said in the last meeting, and what happened, in order.
- Companies have a relationship: Prospect, Customer, Partner or Reseller. A company becomes a customer the moment you change its relationship on its page, and then it shows under Customers, which you can filter by Active or Churned.
- Meetings are write-ups on a company, customer or contact page: what they want, what got done, what is still open.
- The activity timeline is the Activity card on a contact: every change in order, a single save folded into one entry showing the new value and the old one struck through, plus events from your other apps.
upsert_crm_company, upsert_crm_contact (linked with companyRef), then list_crm_companies with the relationship filter.- Open Companies and click Add company; on a company’s page set its relationship.
- Open Customers to see the ones that became customers, partners or resellers; Add customer adds one directly.
- On a contact, company or customer page use the Meetings card, and read the Activity card for the timeline. Both are cards you can place with the page designer.
Shape fields and pages
Every place in the app has two pages: the list you land on and the page for one record. The standard ones work; this is where you make them yours.
upsert_record_field once per field. The calculated one is a formula, daysSince(…) — you never type it.describe_page_blocks, get_page_design, set_page_design. It reads the design first and changes only the part you asked for.create_record_type, upsert_record_field with a link (relation) field, a rollup (sum over the payments) and a formula, and transitions on the status.get_crm_navbar, set_crm_navbar.- Settings → Record design shows one card per place in your navbar, each with its two pages: Main page and Record page, marked Standard or Designed.
- Click Design on the card (or on one of its two pages) to open the designer full screen.
- Pick a layout (Magazine, Spotlight, Portrait, Aurora, Duo, Poster, Dossier, Three column, Trio, Hero + split, Hero + one column, Classic, Sidebar or Stacked), then drag cards and fields where you want them. The page shows example values, not your data.
- Add a field with + New field and press Publish when you are happy.
Do the navbar in the app too: in the workspace settings, choose which tabs show, their order and their names.
Cards worth knowing: Details, Key metrics (big number tiles), Contacts, Source, Tags, Recent conversations, Activity, Meetings, Tasks and History.
Tasks, rules and one dashboard
A CRM that only stores things gets forgotten. Tasks make it a to-do list for the team; rules create those tasks for you at the moment something changes.
A task, by hand
create_crm_task with the assignee, due date, priority and a link to the record.- Open Tasks. Tabs: Today, Overdue, Upcoming, All open, Done; switch between Mine and Everyone, and between List and Calendar.
- Type in Add a task and press Enter, or click New task for the full form: due date, reminder, priority, assigned to, related to (a record), repeat.
A rule that creates the task for you
A rule reads like a sentence: when something happens to a record, only if it matches, then do these things. It acts once per record and event, and rules are created switched off so you can test them first.
create_crm_automation (saved off), test_crm_automation on a record — it changes nothing — and, after your yes, set_crm_automation_enabled.list_crm_automation_runs.- Click Automations in the navbar, then the Record rules tab.
- Under your record type click New rule.
- When: pick what starts it — a record is created, a field changes, a date arrives, a record is linked. Only if: add conditions, or leave none. Then: add the actions in order — create a task, set a field, set a field on a linked record, create a record, or email the team.
- Click Save, then switch the rule On.
One dashboard
list_crm_report_sources, run_crm_report to check each number, then save_crm_dashboard.- Open Dashboard and click Create a dashboard. It suggests first widgets from your own record types and fields.
- Click Add these widgets, or Build my own and use Add widget: pick the data, what to show (count, total, average…) and how to cut it. The preview runs on your real data.
Connect it to your agent and Inbox
The CRM and the Agents app share the same people. The CRM is where you work them; the conversation itself stays in the Agents app.
- A contact’s page lists their latest conversations. Click one and it opens in the Agents app, where the transcript and the reply box live. The CRM never hosts a chat.
- The tags your agent applies show up as chips on the contact and as a filter on the list. Set them up once, in Set up tags.
- Audiences group people. In Contacts, open Audiences → New audience: a dynamic audience is rules (tag, channel, source, phone, email, consent) with a live count; a fixed one is picked by hand.
- Broadcasts reach an audience. From Contacts → Broadcasts, send a WhatsApp template to a whole audience and follow recipients, sent, failed and status in the same list.
- The “CRM Agent” button in the navbar opens an assistant panel for how-to questions and for working with audiences.
Send a broadcast from Claude:
With Claude, you can also just ask the CRM questions:
find_records with filters and ranges, get_record for the people attached.Connect it to your other tools
The CRM is meant to sit in the middle. Things flow in from your other AssistantLabs apps, and out to whatever else you run.
- Sales leads → CRM. In Sales, Leads · CRM decides when a lead becomes a record in the CRM, as what, and which value lands in which field. See the Sales app guide.
- Bookings. Every booking updates the contact and adds a booked / cancelled / completed / no-show event to their timeline.
- Export. The Export button on a list downloads it; with Claude,
export_crm_recordsreturns a record type as a table.
Webhooks: send changes out
A webhook sends new and changed records, and task events, to Make, Zapier, n8n, your accounting software or your own server. Every request is signed, so the other side can check it came from you.
create_crm_webhook, test_crm_webhook. A new webhook starts off; the first successful test switches it on.- Open Settings → Webhooks and click New webhook.
- Give it a name and the https:// address, pick the events (Record added, changed or deleted, Contacts linked or unlinked, Task added, changed, completed or deleted) and, if you want, Only for certain record types.
- Click Create webhook. Only workspace admins can manage webhooks.
For developers: The CRM also has a developer API (companies, contacts, record types, activities, meetings) with keys scoped to crm:* permissions, created in the Agents app’s organization settings.
Invite your team and set roles
Two separate things: getting people into the workspace, and deciding what each of them may open and change.
1. Invite
Do this in the app: in the Agents app, open your organization page and click Invite Member, enter the email and choose the role, member or admin. Once someone is in the workspace, they are in the CRM too.
2. Roles
A role decides which record types a person can view or edit, which fields they never see, whether they open contacts and dashboards, and whether they see everyone’s tasks. Members without a role keep full access and admins always see everything, so nothing changes for anyone until you put them in a role.
get_crm_roles, list_crm_team_members, save_crm_role, assign_crm_role.- Open Settings → Team roles and click New role.
- Name it, set a Default access (No access, View or Edit), override it per record type, and choose Hide fields. Switch Sees everyone’s tasks and Opens the dashboards on or off.
- Under Who holds which role, choose a role for each person.
Your first week
A realistic week for a small business. Each line is one sitting, not a project.
- Day 1 — connect and look. Connect the agent, open Contacts, scroll through ten people you know.
- Day 2 — one record type. Create the one thing you keep most (treatments, properties, deals) and add five real ones by hand.
- Day 3 — import. Bring in the old spreadsheet, dry run first, duplicates on “Fill in what is missing”.
- Day 4 — one rule. The follow-up you always forget. Test it on a real record, then switch it on.
- Day 5 — team. Invite one person and give them a role. Ask them to find a record without your help.
- Day 7 — the numbers. Create the dashboard, and ask yourself which number you actually looked at.
Common mistakes
- A record type for people. Patients, buyers and clients are contacts and customers. A record type is for what you keep about them.
- Linking before the target exists. Create the types others point at first (clients and products before units, units before contracts). The same goes for importing.
- Importing without a dry run. Check first, always. “Add anyway” is only for a list you know is all new people.
- Expecting the address to change. A record type’s “Address in the app” is permanent. The names can be changed any time.
- Switching a rule on untested. A rule acts once per record and event. Run the dry run on a real record first.
- Making roles and expecting a change. Nothing changes until people are put in the role.
- Redesigning a page casually. A page is the app for everyone in the workspace. Review, then publish.