Documentation
How AISOS is set up, what each part connects to and the rules that keep you in control.
How AISOS works
AISOS is a set of AI agents that run inside your team's own Claude workspace. Four pieces do the work:
- Connectors link Claude to the tools you already use: CRM, email, calendar, chat, call recorder and files. They use your own logins and permissions.
- Skills are written playbooks for each job: how to triage a lead, write a recap or name a deal. They hold your rules, so the work comes out the same way every time.
- Scheduled agents run those skills on a timetable, such as every hour for inbound or Tuesday morning for prospecting, and leave the results for you to review.
- Memory keeps the facts the agents should never get wrong: your price list and discount limits, standard contract terms, and what each client has agreed. That's what keeps proposals, contracts and pricing consistent. More on memory
Every message to a client is a draft until a person approves it. That rule is built into each skill, not left to a setting.
Who is AISOS for
AISOS works just as well for founder-led businesses as it does for small start-up teams. Whether you're a one-person team or a start-up with or without a sales team, AISOS can work for you.
Founder-led and one-person teams
You're selling, building and running the company at once. AISOS triages your leads, drafts your follow-ups and keeps the CRM up to date, so selling doesn't stall when the rest of the job gets busy.
Start-ups and small businesses
With a sales team or without one. Every rep gets their own Command Center and voice guide, and the whole team shares one set of rules for pricing, CRM and approvals.
Any industry
AISOS is built around your CRM, your products and your voice, not a single market. It fits crypto, fintech and data companies as well as SaaS, logistics, retail and professional services.
AISOS also scales to larger companies. Some features may need your IT team's approval and your own data security review before they go live.
Before you start
Every setup starts with the intake form, which takes about 10 minutes and covers your business, your sales process and the tools we'll connect. Once you sign on, have these ready before week 1:
- Claude Team (or Enterprise) seats for each person who will use the system
- Admin access to the tools you want connected, or someone on call who has it
- 30–50 recent sent emails per rep, for the voice guide
- Your price list and any proposal or contract templates
- One person who owns your rules and playbook: when pricing can appear, how deals are named, who gets which leads
Write like me: the voice guide
Drafts only save time if you don't have to rewrite them. Each rep gets a voice guide built from their own sent emails.
What it captures
- Greetings, sign-offs and typical length
- Words and phrases you use, and ones you never would
- How you handle each situation: first reply, follow-up, chaser, polite no, pricing question
- Formatting habits, such as bullet points or none, and links inline or at the end
How it improves
When you edit a draft before sending, tell the agent what you changed and it updates the guide. After a couple of weeks most drafts go out with light edits or none.
Connecting your CRM
AISOS works with Salesforce, HubSpot, Pipedrive and Attio, and with other CRMs that have an API.
What it reads and writes
- Reads: accounts, contacts, open deals, activity history and owners, to check history before any outreach
- Writes: new leads and contacts, deal stage, next step, close date and call notes
Rules we set together
- Naming conventions for accounts and deals
- Required fields, and what counts as a qualified lead
- Duplicate checks before anything is created
- Which changes need a person's approval, such as stage moves or amounts
We recommend a dedicated integration user with only the permissions the agents need.
Email and calendar
Gmail, Google Calendar, Outlook and Microsoft 365 are supported.
- Replies and sequences are saved as drafts in your mailbox. You send them, or approve them for sending.
- Optional labels keep agent drafts and triaged leads easy to find.
- The calendar is used to prepare for meetings, find follow-up slots and add reminders. It doesn't accept or decline invites for you.
- Scheduling links such as Calendly can be added to drafts automatically.
Slack and Telegram
The days of cold calling are over. Messages and alerts go where your team already communicates.
Slack
- One morning message per rep with their top three for the day
- Alerts for qualified leads, and weekly report links in a team channel
- You choose which events send a message, so it stays quiet
Telegram
For teams that already work with clients on Telegram, AISOS joins in through your own Telegram bot. It can sit in client group chats, or work for you as a 1:1 assistant.
Setting up your bot
- Create it. Open @BotFather in Telegram, send
/newbot, and choose a name and username, such as "Acme Sales Assistant". BotFather gives you a token. - Connect it. We add the token to the Telegram connector in your Claude workspace. It stays there, never in an email or a shared doc.
- Choose what it can see. In a group, a bot only receives messages that mention it, reply to it or start with a
/command. To let it follow the whole conversation, turn off privacy mode in BotFather (/setprivacy) or make the bot a group admin.
In client group chats
- Add the bot to the group like any member, and let the client know it's there
- It logs the conversation against the right CRM account, flags questions still waiting on you in the Command Center, and drafts replies
- Drafts come to you first. The bot only posts in the group after you approve
As your 1:1 assistant
- Message the bot directly: "what's my next meeting?", "draft a reply to the fund", "summarise today's partner group"
- Get lead alerts and approve drafts from your phone, wherever you are
- Telegram doesn't let a bot message someone first, so each person on your team opens a chat with the bot once to switch it on
Whichever channel you use, messages to clients follow the same rule as email: drafts until you approve.
Call recorder
Fathom, Zoom, Gong and Microsoft Teams recordings can feed the recap workflow.
- Type
meeting notesafter a call to get the recap in chat and a dated document in your Meeting Notes folder - Recaps follow a set format: attendees with roles, background, discussion, decisions, next steps with owners
- Transcript errors in names and terms are fixed using your CRM and email history
Knowledge bank and files
The agents answer questions from your own material, not from the internet. We set up one shared folder in Google Drive, SharePoint or Notion with:
- Product sheets, FAQs and the answers you give most often
- The current price list and discount rules
- Case studies and approved customer references
- Proposal, contract and order form templates
Each file is marked as either OK to quote to clients or internal only. Old versions are archived so the agents never use an outdated price.
Scheduled agents
A typical timetable. Every item can be moved, paused or switched off.
| Agent | When | What it leaves for you |
|---|---|---|
| Inbound triage | Every hour | Reply drafts and lead alerts |
| Outbound prospecting | Every weekday morning | Researched prospects with sequences |
| Command Center | Every weekday morning | Your page and one message |
| Call recaps | After each recorded call | Recap, follow-up draft, CRM update |
| Weekly report | An hour before the meeting | Updated numbers and flags |
How it looks in the Command Center
| Task | Today | Sat | Sun | Mon | Tue | Wed | Thu |
|---|---|---|---|---|---|---|---|
| Inbound lead triage | 14 | 6 | 6 | 14 | 14 | 14 | 14 |
| Morning briefing | 1 | · | · | 1 | 1 | 1 | 1 |
| Outbound prospecting | 1 | · | · | 1 | 1 | 1 | 1 |
| Call recaps | 2 | · | · | 3 | 2 | 2 | 1 |
| Weekly pipeline report | · | · | · | · | · | · | 1 |
| Total runs | 18 | 6 | 6 | 19 | 18 | 18 | 18 |
Memory and standing rules
Some things should only be said once. AISOS keeps them in memory and applies them to every run, so each proposal, contract and reply starts from the same facts.
What it remembers
- Pricing: your current price list, discount limits and who can approve more, so proposals use today's prices
- Contract terms: standard payment terms, renewal and notice periods, and the clauses you won't change
- Each client's deal: what was agreed, any special terms, renewal dates and who signs, so the next proposal picks up where the last one left off
- Your business: product names, territories and who covers which accounts
- Preferences and corrections: such as "no pricing in the first email" or "always copy my manager on enterprise deals". A mistake fixed once stays fixed
To change something, say so in plain English, such as "our annual plan is now $12,000". Personal and sensitive details are not stored as memory.
Commands you can say
Some workflows run when you ask. Say the phrase in any Claude chat and the matching playbook runs, following your rules.
Pulls your latest call recording, posts the recap and saves it to your Meeting Notes folder.
Drafts any email or message in your voice, using your voice guide.
Creates the account, contact and deal in your CRM with your naming rules.
First draft from your template, your current price list and what was agreed on calls.
Re-ranks your Command Center with the latest inbox, chat and calendar.
While you're out: drafts replies, preps tomorrow's meetings and tidies the CRM.
Custom agents and workflows
Every team sells a little differently. If you need an agent, a workflow or a rule that isn't on this page, we build it. Custom work is part of every setup.
The intake form
Each request starts with the intake form and a short call. Together they cover:
- The job: what the agent should do, in a sentence or two
- The trigger: a schedule, an event such as a new lead or a signed contract, or a phrase you say
- What it reads: the tools, folders and records it needs
- Your rules: what it must always do, and what it must never do
- The output: where the result lands, and who approves it
- Examples: two or three real cases, good and bad, to test against
We build it, test it on your examples, and tune it during its first week of real use.
Start with one, then copy it
The fastest way to grow is to get one campaign or call format right, then copy it. We set up your first outbound campaign or call playbook together and check the results. After that, each new version is a copy where only the differences change:
| New version | What you change |
|---|---|
| A new target market | Target profile, opening hook, case study |
| A new product | Value points, pricing, discovery questions |
| A new region or language | Language, send times, local references |
| A new call type | Agenda, recap headings, follow-up email |
Your voice, CRM rules and approval step carry over to every copy, so each new version is much quicker to launch than the first.
Proposals and contracts
- First drafts are built from your templates, the current price list and what was agreed on calls
- Versions are named consistently, so the latest is always obvious
- Anything with a price or legal terms is reviewed by a person before it leaves
- Signed paperwork can be tracked through DocuSign and logged in the CRM
Security and your data
- Everything runs in your own Claude workspace, under your account and your admin controls
- Connectors use your own logins and permissions. Disconnect any of them at any time
- Nothing is sent to a client without a person's approval
- Your data is never used for another client's setup
- Business plans for Claude do not train models on your data by default. Check your plan's terms with your admin
Where output lands
Every destination is listed in the Command Center. Amber boxes are places a task writes without asking first; everything else waits for you.
Email drafts
- Inbound lead triage
- Outbound prospecting
- Call recaps
- Away mode
CRM
- New leads and contacts
- Deal stage and next step
- Away mode field updates
Command Center
- Morning briefing
- Every task's results
- Reports tab
Slack or Telegram
- One morning message
- Qualified lead alerts
Meeting Notes folder
- Call recaps
- Weekly pipeline report
Prospect tracker
- Outbound prospecting
Support and changes
Teams on monthly support get tuning and fixes. Ask for changes by email or Telegram, in plain English, such as "add a fourth email to the sequence" or "send inbound alerts to the EU channel".
Questions before you start? Write to sales@aisalesos.net.