Inbound Desk Official

Salesv1.0.012 components

Inbound for a founder or a small GTM team. A lead lands from your website form, a demo request, a booking or a referral; within a minute the desk has enriched the company, scored the fit against your ICP, picked an owner and drafted the first reply with two slots. You read it and send it from your own inbox. Leads that go quiet get a nudge drafted, demos get a one-page brief, and Monday tells you which sources bring the leads that book. Your CRM stays the record. Comes with Ines, an Inbound Coordinator.

Installs in about 20 min, verified with a smoke test.

Install this pack How the install works

How the pack is wired

One named coworker, the agents it orchestrates, and the data, knowledge, and tools underneath. This is the real manifest, not a mockup.

AI EmployeeInes, Inbound Coordinator coordinator
AgentsLead ScorerReply SenderGo-cold ChaserDemo Brief WriterCRM SyncWeekly Inbound Digest
Data & KnowledgeLeads read/writeFollow-ups read/writeDemos read/writeSources read/writeInbound Playbook RAG
ToolsGmailHubspotApolloHunterGoogle CalendarTurtle Notify

The employee routes each request to the right worker. Agents read and write the tables, ground answers in the knowledge bases, and act through your connected tools. Every write is gated and traced.

The full blueprint

Every agent's tasks, every table's schema, every trigger. Read it all before you sign in.

Ines, Inbound Coordinator

Quick, warm, precise. Ines knows which lead is waiting on whom, why a lead scored the way it did, and never lets a good one go cold.

5 agents · 4 tables · 1 KBs
Lead Scorer
Inbound SDR who answers within the minute and never oversells
2 tasks · 6 in

Enriches the company, scores ICP fit from the playbook, picks the owner, and drafts the first reply as a Follow-ups row for the owner to send.

LeadsFollow UpsApolloHunter
  1. 01New lead: {{name}} <{{email}}> from {{company}} ({{website}}), source {{source}}. Message: {{message}} Enrich the company from the email domain or website with Apollo; verify the email with Hunter. Read the Inbound Playbook and score the fit (A, B, C, Not a fit) with a one-line reason. Decide the owner by the playbook's rule. Output: The enrichment (size, industry, funding, location), the verification result, the fit with its reason, and the owner, as plain text lines.
  2. 02Update the lead row: Company (if it was blank), Website, Company Size, Industry, ICP Fit, Received (today if blank). Then draft the first reply in the playbook's voice (answer their question first, under 90 words, one example if it fits, two slots and the booking link; for Not a fit, the polite no). Create a Follow-ups row: Follow-up ("{{name}} · first reply"), Lead, Kind First reply, Subject, Body, Status Drafted, Due today. For Not a fit set the lead's Status to Disqualified. Write a three-line summary. Plain text. Output: The three-line summary, plain text.
Reply Sender
Mail clerk who sends what was approved, unchanged
2 tasks · 6 in

Sends exactly the approved subject and body from the approver's own Gmail, records the send, and updates the lead. Runs only when a person approves a follow-up.

LeadsFollow UpsGmail
  1. 01Follow-up {{follow_up}} ({{kind}}) for {{lead}}, status {{status}}. Subject: {{subject}} Body: {{body}} Read the lead's Email. If the status is Approved, send the email with Gmail exactly as given. Output: Whether it was sent, to which address, and the message id, or why not. Plain text.
  2. 02Update the follow-up: Status Sent and Sent At today when sent; Bounced with the reason when the send failed. When sent, set the lead's First Reply At if blank and move Status from New to Replied. Write a one-line send log. Plain text. Output: The one-line send log, plain text.
Go-cold Chaser
Follow-up writer who never nags twice
2 tasks · 5 in

For a lead replied to two business days ago with nothing since, drafts the nudge as a Follow-ups row. Never sends.

LeadsFollow Ups
  1. 01Lead {{name}} at {{company}}, status {{status}}, first reply {{first_reply_at}}. Read this lead's Follow-ups. Decide whether a nudge is due: first reply two or more business days ago, no Nudge row yet, and no Sent follow-up in the last two business days. Output: Whether a nudge is due and why, plain text.
  2. 02If due, create a Follow-ups row: Follow-up ("{{name}} · nudge"), Lead, Kind Nudge, Subject ("Re: " and the first reply's subject), Body in the playbook's voice (one line, the booking link, an easy out), Status Drafted, Due today. Otherwise change nothing. Write one line saying what you did. Plain text. Output: One line, plain text.
Demo Brief Writer
Chief of staff who preps the founder for a call
2 tasks · 4 in

What they asked, who they are, what we said, the likely objections and the pack or plan to show.

LeadsFollow UpsDemosApollo
  1. 01Demo "{{demo}}" ({{kind}}) with {{lead}} on {{when}}. Read the lead's row (message, enrichment, fit) and their Follow-ups. Output: The facts gathered, plain text.
  2. 02Write the brief: Who they are, What they asked, What we said, What to show first, Three questions, Two likely objections with the playbook's answer. Under 300 words, plain text. Set the lead's Status to Booked. Output: The brief, plain text.
CRM Sync
RevOps clerk who keeps one source of truth
2 tasks · 7 in

Creates or updates the contact, the company and the deal in the CRM when a lead's status changes.

LeadsHubspot
  1. 01Lead {{name}} <{{email}}> at {{company}} ({{website}}) moved to {{status}}, fit {{icp_fit}}, existing link {{crm_link}}. Find or create the contact and the company. Create the deal if the status is Replied or later and there is none; otherwise update its stage. Never delete. Output: What was created or updated, with the record links, plain text.
  2. 02Write the contact or deal link into the lead's CRM Link and a one-line log. Plain text.Output: The one-line log, plain text.
Weekly Inbound Digest
Founder's analyst
2 tasks

Leads by source and fit, median first-reply time, demos booked and held, what went quiet, and which sources bring the leads that book.

LeadsFollow UpsDemosSourcesTurtle Notify
  1. 01Count from the tables: Leads with Received in the last 7 days by Source and by ICP Fit; median days from Received to First Reply At for those; Follow-ups Drafted with Due before today; Demos with Outcome Held, No show, and Pending with When in the next 7 days; leads in Nurture. Update each Sources row's Leads This Month and Booked This Month from the Leads and Demos tables for the current month. Output: The counts, as plain text lines.
  2. 02Write the digest: the numbers as short lines, "First reply:" the median, "Sources:" one line each with leads, booked and cost per booked meeting, "Quiet:" the overdue drafts, "This week:" the demos. Then "Decide this week:" at most three. Under 250 words, plain text. Send it with Turtle Notify and confirm. Output: The digest text and a confirmation that it was sent, plain text.
Leads
Every inbound lead from every source. Enriched and scored on arrival; the owner replies from the queue.
16 cols
Name textEmail emailCompany textWebsite textMessage textSource selectICP Fit selectCompany Size textIndustry textEnrichment agent_outputOwner userStatus selectReceived dateFirst Reply At dateCRM Link urlCRM agent_output
Follow-ups
Every message to a lead, drafted by the desk. Approving one sends it from the owner's own inbox; nothing leaves without that click.
10 cols
Follow-up textLead foreign_keyKind selectSubject textBody textStatus selectDue dateSent At dateApproved By userSend Log agent_output
Demos
Booked calls with a one-page brief written from the lead, the enrichment and the messages so far.
7 cols
Demo textLead foreign_keyWhen dateKind selectBrief agent_outputOutcome selectNotes text
Sources
Where leads come from and what each source costs, so Monday can say which ones bring the leads that book.
6 cols
Source textChannel selectMonthly Cost numberLeads This Month numberBooked This Month numberNotes text
Inbound Playbook

Who is a fit, how we reply, the slots we offer and what we never promise. Replace the starter text with your own.

2 sources

How the install works

  1. Overview. You see the entire department before anything is created: every component, every tool it needs connected.
  2. Setup questions. A few plain-language choices set your sources, limits, and approval gates, so the department arrives configured for your rules, not defaults.
  3. Conflicts. Nothing in your workspace gets clobbered: anything that already exists, you keep, rename, or replace.
  4. Install. Tables → knowledge → agents → wiring → employee, in dependency order, ending in a smoke test that proves it works.
  5. Done. A working department, not a project plan. Open your new coworker and assign the first task.

Setup asks the governance question before anything runs: for example, should the employee require human approval before sending external emails?

Built on

Connects to

GmailHubspotApolloHunterGoogle CalendarTurtle Notify

Governance defaults

  • Per-table Read / Create / Update / Delete grants, Delete off by default
  • Approval gates on external writes (email, records) until you loosen them
  • Budget ceiling and run-trace on every component

More like this

All packs
Outbound Desk
Sales~25 min
Signal-based outbound for a founder or a small GTM team. Every morning the desk finds the accounts with a reason to write now (hiring, funding, news, a post), finds and verifies two contacts per account, and drafts a three step sequence in your playbook's voice. You approve, and the email goes from your own inbox. Replies land in one queue, classified with the next step ready. Meetings get a one-page brief. Your CRM stays the record. Comes with Remy, an Outbound Coordinator who runs the morning queue.
Sales Calls and Pipeline Desk
Sales~25 min
The sales manager's pipeline, kept honest. Every call is summarised the moment it is logged: what was said, the objections, the next steps with dates, and the CRM note and follow-up task drafted for a person to approve. Every weekday morning the deals that have gone quiet, or whose close date has passed, get a nudge drafted for the owner and a touch drafted for the customer. Before a meeting, the contact is enriched and a one-page brief is written. When a deal changes stage, the sequence follows: paused at Meeting or Closed, flagged when the deal is Lost. Every Friday the review pack is written: the numbers, the slipped deals with reasons, three decisions. Works with your CRM (HubSpot, Pipedrive, Zoho CRM, Close, Copper, Attio and others), your call notes tool (Gong, Fireflies, Fathom), your sequencer (Salesloft, lemlist, Amplemarket), your enrichment tool (Apollo, Lusha) and your phone tool (Aircall, Dialpad, JustCall). No agent changes a deal amount, closes a deal, moves an owner or sends a customer a word without a person. Comes with Ari, a Sales Ops Coordinator.