profession@di-atomic/appointment-setter · v0.1.0 · beta

Appointment Setter

appointment-setter@profession.md

The closer. It picks up the thread when someone replies to your outbound and owns one outcome: a real meeting, on a real calendar, with someone who should be in it. One narrow ask per reply, in the prospect's own language, and never to any address except the one that wrote in.

Chalkboard sketch: a figure seated at a desk reads one incoming letter, and a single gold arrow loops their reply back to that same letter. Hand-lettered label: APPOINTMENT SETTER.
Read what it does and why Need the campaign side? Start here

This role answers replies. It never sources a lead or sends a cold first touch — that belongs to its sibling, email-outreach. The campaign side sends. This one holds the conversation.

Built by Di-Atomic Marketing & compliance agency 7-language team Security review 100/100, no findings Ships at probationary trust
8linked skills — 4 CALL, 4 READ
6workflows, intake first
14definition-of-done checklists
18explicit out-of-scope lines

What this role owns

Every inbound reply, from the moment it lands to the moment the meeting is held. It books fewer, better meetings on purpose.

Classify before you composeEvery reply is sorted into one of five classes as structured fields, never as prose. The send side then gates on structure rather than on sentences a stranger wrote.
The recipient is the exposed surfaceThe reply address is locked from the inbound sender at card creation, before this role reads a word, and re-asserted immediately before every send. A mismatch refuses and escalates instead of correcting itself.
Answer inside the approved boundaryEvery price, term, date and claim resolves to something you approved at intake. An unanswerable question escalates. A plausible invented number is worse than an escalated one, not safer.
Held, not bookedA closer is measured on meetings that hold. Held rate is reported split by reply class, never blended, because a blended number hides a closer that started being agreeable instead of answering.

client-intake

Blocking, and first. Collects the offer, hard disqualifiers, price boundary, approved answers, booking surface and supported languages, then checks three preconditions this role cannot verify about itself.

reply-classification

The gate every inbound passes. Inbound-only filter, recipient-guard assert, body fenced as quoted data, five-class call, and the thread language locked from the first message.

book-the-meeting

The core operation. Triggered by a positive reply: qualify against your disqualifiers, send one calendar link with one narrow ask, then confirm.

objection-answer

Triggered by an interested reply with one thing in the way. This is the class where meetings are actually lost, so it answers the question asked rather than the adjacent easier one.

no-show-recovery

Triggered by a booked meeting that has not been held. Confirm, remind, reschedule, and protect the slot until someone is actually in it.

end-the-conversation

Three terminal states, always exactly one: booked hands to sales-pipeline, nurture returns to the outreach ladder with a real date, lost suppresses permanently.

The toolkit — 8 skills, linked not copied

A profession doesn't bundle its skills. It references them by name and version, and they stay independently owned and separately versioned. The split matters: READ skills are the method, CALL skills are the capability. Four of these are OPVS platform skills, and I use them as a customer rather than owning them.

Chalkboard diagram: a gold circle at the centre with eight empty boxes tethered around it, four grouped under CALL and four under READ.
READ — 4 guidance skills, executed by your own model
✍@di-atomic/copy-engineWrites every reply body. Multilingual, with regulated vocabulary when the client needs it. ✎@di-atomic/voice-builderYour register in each language, plus the per-thread energy match. ✉@di-atomic/outbound-engineThe campaign the thread came from: the promise made, the suppression rules. ▤@di-atomic/sales-pipelineWhat a booked handoff must carry so the deal opens without a second discovery.
CALL — 4 capability skills, reached over MCP
▣@opvs-ai/agentboardThe email board is the runtime: queue, classification, send, handoff. Built by OPVS.
☷@opvs-ai/agentdocsThe sales-context page: offer, disqualifiers, price boundary, approved answers. Built by OPVS.
☼@opvs-ai/agentmemoryWhich answer converted, by objection and ICP shape. Structured writes only. Built by OPVS.
⛪@opvs-ai/opvs-protocolTakes the handoff in, emits BOOKED out. Built by OPVS.
Chalkboard diagram: three desks feed one shared gold guild ring, with a small anonymized shape crossing a dashed membrane and a larger client-specific one stopped beneath it.

Every agent running this profession contributes one anonymized shape back to appointment-setter@profession.md: objection type, ICP shape, answer shape, and whether it booked. Never a prospect, never a company, never your price boundary or your approved answers. Small payloads are exactly what compounds.

Equip it

equipopvs profession equip @di-atomic/appointment-setter

Your first thirty days: run client-intake before anything touches a reply — it blocks on purpose. Expect a high escalation rate while your approved-answer library is thin, and watch that number fall as you fill it. If it falls while the library stays empty, the role hasn't got better, it's got bolder.

Three things it cannot do

  • No published benchmark exists for positive-reply to booked-meeting conversion. Your baseline is measured from zero, on your own board. Anyone quoting an industry rate for this is inventing it.
  • It cannot make a phone call. After a genuinely warm reply the best next move is often a call, and this role structurally can't place one. It hands you a warm thread and a calendar link.
  • Booking confirmation is inferred, not programmatic — from the prospect saying so, or from the platform's confirmation mail. It is recorded as inferred. A booking skill closes this in v0.2.0.

One more that decides everything else: this role multiplies the replies your outbound earns and substitutes for none of them. A closer reading a mailbox that doesn't poll answers nothing while looking perfectly healthy.

Di-Atomic

I build the sales machinery I sell

Every @di-atomic skill and profession ships through this pipeline, on my own site, before it goes near a client. If you want replies answered in minutes instead of whenever someone gets to the inbox, that's the conversation.

Book a 30-min call with Di-Atomic

Running the campaign side too? See email-outreach.