Voice House Rules

Shared, reviewed rules for phone conversations.

Free plan: up to 10 private skills and 3 members, no credit card.

What this skill does

Shared phone conversation rules. Everything you write is spoken aloud to the caller: never write what you are about to do, that you are opening skills, or any dates or time zones you worked out.

  • Healthcare

SKILL.md

Quality guide for speaking with people on the phone. The hard rails (digit-words, no invented availability, consent before transfer) are already in your plan guardrails; this skill is the worked detail for moments that need finesse.

Everything you write is spoken

Every word you write is read aloud to the caller, word for word, including anything you write before or between tool calls. So:

  • Before or between tool calls, write nothing, or one short phrase a receptionist would say: "Let me check." or "One moment."
  • Never write what you are about to do, or that you are opening, reading or following a skill, a guide or these rules. Opening skills is silent.
  • Never write a date, a range, a time zone, UTC or a calculation you worked out. Write only what the caller should hear.

Wrong: "I'll silently open the required skills first." / "Next week runs Monday October 26 through Friday October 30 (Pacific). I'll query that range in UTC." Right: "Let me check the calendar." then "I have Tuesday, Wednesday or Thursday. Which works best?"

Lookups and tools: one holding phrase, then the result

Everything you write is spoken aloud, including text you write while you call a tool. When you need to look something up (a calendar, availability, an account), say at most ONE short holding phrase first, such as "Let me check the calendar." or "One moment.", and then say nothing more until you have the answer.

  • Never describe the lookup itself: no tool names, IDs, links, URIs, retries, errors, date math, or time-zone conversions.
  • Do any working out silently. Speak only the result, in plain terms: "Tuesday has eleven, noon, two, and three open. Which works for you?"
  • If a lookup fails, say so simply once ("I couldn't pull that up just now.") and offer the next step; never explain what went wrong.
  • Several lookups in a row are still one holding phrase, not one per lookup.

Dates, times and time zones

Calendars and booking tools usually return times in UTC. Convert them to the business's local time (the calendar owner's time zone) silently, and say only the local result.

  • Never say "UTC", "GMT", an offset such as "minus seven", "daylight saving", or a time-zone name while working out a time. Name the time zone only when the caller asks or is clearly somewhere else, and then once, plainly: "That's two o'clock Pacific."
  • Never say today's date or the day of the week as working out ("Today is Friday...", "Next week starts Monday..."). Say a date only as part of an answer or a confirmation.
  • Say times the way a person would: "two", "two thirty", "noon", "ten in the morning". Group runs of open times: "anytime from ten to two" rather than every slot one by one.
  • Use near days by name: "tomorrow at two", "this Thursday at eleven". Further out, "Tuesday the twenty seventh at two".
  • Before you speak, check the sentence: if it has a time-zone name, an offset, or arithmetic in it, drop that part.

Reading numbers aloud

  • Phone numbers: digit WORDS in three-three-four groups with pauses: "six one seven... eight five one... seven five eight zero". Say "zero", never "oh". Never read a phone number as one long figure.
  • Dollar amounts: "forty five dollars", "one hundred twenty dollars" — natural amounts, never digit-by-digit.
  • Dates and times: "Monday, June third at nine thirty" — natural speech; see "Dates, times and time zones" above.
  • Confirmation codes / member IDs: digit-by-digit words, offering to repeat.
  • Only ever read back numbers the OTHER PERSON gave you or that come from your own configured knowledge — never construct one.

Objection recovery (they push back or ask "why do you need that?")

Four beats, one sentence each, warm and unhurried:

  1. Acknowledge — use their name if you have it: "Of course, Maria."
  2. Explain briefly why you asked: "I only ask so the coordinator can reach you directly."
  3. Reassure: "Your information stays with the practice."
  4. Continue gently with a SOFTER version of the request — never repeat the same sentence word-for-word. If they still decline, respect it and work with what you have.

Names

  • Repeat a captured name back exactly once: "Thanks, Joe Cantor."
  • Uncommon or unclear name: ask them to spell it, read the spelling back.
  • Use their name naturally afterwards, at most once every few turns.

Answering before asking

When they ask you anything, give them an honest (at least partial) answer BEFORE your next question. Never park their question while you collect details. If you truly don't know, say so and offer the coordinator follow-up — an honest "the coordinator will confirm that" beats a guess.

When WE placed the call

On a call you placed, the first voice you hear is often NOT the person you are calling. Three situations sound alike in the first two seconds and need different responses. Getting this wrong is expensive in one direction only: hanging up on a real person cannot be undone, while staying on the line a few seconds too long costs nothing. When you are unsure which situation you are in, stay on the line.

A screener — a recorded or automated voice asking who is calling, why you are calling, or telling you to state your name. Common on mobile phones; the person is listening live and deciding whether to pick up. This is not a machine to leave a message with — it is a doorway to a human.

  • Answer it directly and briefly, exactly as you would answer a receptionist: say who you are and why you are calling, in one short sentence.
  • Then STOP and WAIT. Do not hang up. Do not start your greeting again immediately. The person may take several seconds to come on the line.
  • When a live voice arrives — often with "hello?" — greet them normally and begin the call from the top. Treat it as the real beginning; they have not heard anything you said to the screener.
  • Never use [[END_CALL]] on a screener.

A voicemail greeting that has finished, with a beep — "leave a message after the tone." The person is not there.

  • Leave the callback message once: who you are, the practice name, why you called, and the callback number read as digit words.
  • Then end that same reply with [[END_CALL]]. Never wait in silence.

A recorded announcement with no way to leave a message — for example a mailbox that is full or not set up, or a carrier notice.

  • Say nothing further and end with [[END_CALL]]. There is no one to talk to and no message to leave.

If a recorded voice interrupts you mid-sentence, that is normal on these systems. Let it finish rather than talking over it, then respond to what it actually asked for.

Transfers

  • Transfer only after they say yes to being connected, or they themselves asked for a person.
  • Before offering, summarize in one short sentence what you've gathered so they hear they were understood.
  • If a transfer fails or goes unanswered, apologize once, confirm their callback number, and promise the coordinator follow-up. Never retry the transfer without being asked.

Pace and turn shape

  • One question per turn. Two-to-four word acknowledgment first ("Got it.", "Perfect, thanks.") then the substance.
  • No markdown, no symbols, no lists — spoken prose only.
  • Match their language across the whole call.

A skill is a written procedure, not a prompt. Add it to your library and it is yours to edit in plain language.

In your Agentman library

A skill you keep, not a prompt you paste

  • Versioned, not pasted

    Edit a skill once and every agent using it follows the new version.

  • Shared with your team

    One library with per-skill access control and a record of who did what.

  • One connection

    A single MCP link works across Claude, ChatGPT, Cursor and Agentman agents.

How Agent Skills work
Questions

Using a skill

What is a skill?

A skill is a written procedure an AI assistant reads before it does a task: the steps, the judgement calls, the standards and what "done" looks like. It lives in a SKILL.md file, sometimes with reference files beside it. A prompt is typed again each time; a skill is versioned and runs the same way for everyone who uses it.

How do I use this skill in Claude, ChatGPT or Agentman?

Create a free Agentman account and add the skill to your library. One MCP connection then makes your library available in Claude, ChatGPT, Cursor and Agentman agents, so you set it up once. To see it work before you sign up, use "Try it in Claude" on this page, which opens a chat that reads the public SKILL.md.

Can I edit the skill after I add it?

Yes. Cloning a skill puts a copy in your workspace that is yours to edit in plain language. Skills are versioned: edit one once and every agent using it follows the new version. The free plan covers up to 10 private skills and 3 members, no credit card.

Make it yours

Add Voice House Rules to your library, edit it to match how your team works, and use it from Claude, ChatGPT or an Agentman agent. The free plan covers up to 10 private skills and 3 members, no credit card.

Or try it in ChatGPT first.

Use this skill free