Guides
Contacts and portals
Ask questions of your contact list, give your apps their own tables, and set up a portal where your customers sign in and see only their own records. With the SDK, these are the two halves of the same thing.
Contacts, and with it your apps' own tables and portals, is reaching accounts in stages. If it isn't on your account yet, Claude says so, and so does the hub.
Your contact list, in numbers
How many people joined our list this month, by plan?
On every plan, awesomate_crm_metrics and awesomate_crm_query answer with counts and totals, and awesomate_crm_rows looks people up. Claude only sees the fields you've marked readable by AI under Contacts, Your fields, never anything marked sensitive. awesomate_crm_metrics (dataset) also says how many people the list holds and over what dates. awesomate_crm_schema lists exactly those fields, and for a project built with the SDK, awesomate_crm_types writes them out as TypeScript types.
Write descriptions for my contact fields, and group them into sections.
awesomate_crm_layout reads and saves what each kind of record means: the kind itself, its sections, and each field and connection, in your own words. Claude drafts the words, shows you, and saves on your yes (Support Plus and above). It only describes fields AI may read; the ones kept from AI are yours to describe in the hub, under Contacts, Your fields, Sections and descriptions, which also has a Suggest descriptions button.
Your app's own tables (Support Plus and above)
I want to keep track of jobs: a title, a status and a quote, for each customer.
Claude designs the table with you, then creates it (awesomate_crm_kinds). There's no database to set up and no code. It writes records with awesomate_crm_write, saves queries you'll reuse (awesomate_crm_queries), and saves recipes: several writes that happen together or not at all (awesomate_crm_recipes).
A portal your customers sign in to (Pro and above)
Make a portal where my customers can see their own jobs and message us about them.
The awesomate-portals skill takes Claude through it: the tables, the rules about who sees what (awesomate_crm_kinds, set_access), the app and its address (awesomate_crm_apps), the people who can sign in (awesomate_crm_app_users) and the page itself, built with the Awesomate SDK. The rules live in your database, so a customer only ever sees their own records. The tutorial builds one from start to finish.
Then, optionally:
- An AI in the conversations (
awesomate_crm_assistant), answering customers from your Knowledge, either drafting replies for your team or replying itself when it's sure. Ask how much it did this month (usage): replies, the ones that used your Knowledge, and whether it ran on your own AI key. - Reply emails (
awesomate_crm_notifications): when someone replies and the other side isn't in the app, they get an email. - Record events to your n8n (
awesomate_crm_hooks): a new job can start an automation, such as drafting a quote. - Talking by voice: pick one of your agents for the app (
awesomate_crm_apps,voice_agent_id).
Bookings
Set up online bookings for our two treatment rooms, 9 to 5 on weekdays.
Who's booked in tomorrow?
awesomate_bookings runs your own booking diary: customers book an appointment or a class on your website, get an email with a link to change or cancel, and each booking lands in Contacts linked to the person. Claude sets up the calendars (a person, room or resource with its weekly hours) and the services, gives you the booking box to put on your website, and books, moves or cancels for you. Reading is on every plan; changing anything is Support Plus and above. The awesomate-bookings skill takes Claude through it. Bookings are reaching accounts in stages; if they aren't on yours yet, Claude says so.
Your customers' support inbox
Anything waiting in our support inbox?
When your support address forwards to the hub, your customers' emails become tickets there, under Contacts, Support. awesomate_support_desk reads that inbox: what's open, a ticket's messages and notes, and any reply your AI is holding for your OK. It only reads. Replying, sending a held reply and closing tickets are done by a person in the hub. (Tickets to Awesomate are a different thing: see Getting help.) Support Plus and above, reaching accounts in stages.
Email to a list
Draft an email to everyone on our newsletter list about the winter sale.
awesomate_crm_email writes a draft and gives you a link to review it in the hub. Claude never sends: nobody gets it until you've sent yourself a test and approved that exact version.
Tell Contacts what happened (Support Plus and above)
Sam Lee just paid for job 41. Let Contacts know.
awesomate_crm_write, event, tells Contacts that something happened to a person (a job paid, a quote sent), adding them by email if they're new. Any email series you've switched on for that event starts for them, so Claude checks with you first. An event never signs anyone up for email: a series only emails people it's allowed to. Your automations can send the same events.
Bookings
Who's booked in tomorrow? Mark Jo's 10 o'clock as a no-show.
awesomate_bookings reads your booking diary and a single booking with the customer's answers, books, moves and cancels, and records how a booking went (completed or no-show). It can set how often start times fall (every 5 to 60 minutes), the order services show in, and move a booking to another calendar. With your yes, it can unlink a Google or Microsoft calendar from one of yours (disconnect_calendar); connecting one is done in the hub. Reading is on every plan; changes are Support Plus and above.
Every tool is in Contacts, apps and portals.