Examples

Reading a feature list tells you what a product can do. Reading a call tells you what it does. These pages are illustrative calls, written to show the settings, and each one is labelled that way at the top. You'll see the caller's lines, GreetKeeper's lines, and beside each exchange a note on the setting that produced it.

The first four cover the calls that decide whether an answering service earns its keep. An after-hours emergency, where the assistant sorts a flooded kitchen from a dripping tap and texts the on-call plumber. A new-patient booking, where it collects the details, reads the name, number and time back, and writes the appointment into the calendar. A caller who asks for a person, where it transfers to your team and tries a second number when the first doesn't pick up. And a spam call, where a silent or robotic caller is dropped before the greeting and never counts toward your plan.

Under each transcript sits a what-happened list, in the same shape as the call log in your own account: booked, flagged, texted or screened. Then a settings section names each control involved: the hours on that number, the greeting, the question that sorted urgent from routine, the second transfer number and the calendar the booking landed in. Nothing in the call happens without a setting you could change, and the page points at each one.

One outcome shows up on most of these pages: the text messages. When a call ends, the on-call person gets a text with the caller's details. The caller gets one SMS with the booking link or the booking confirmation, and a reply with the opt-out word stops any further texts. Example pages show both messages as they'd read on a phone.

Every capability shown in an example is one you'll find in your own account: answering every inbound call at any hour, answering calls that arrive together so nobody queues, booking into Google Calendar or Outlook, transferring, texting and screening. Examples stay inside that list, which is what makes them a fair preview.

A written call can show a setting at its clearest. It can put a difficult caller on the line on purpose and show the transfer working. And it stays a scenario, built from how these calls tend to go and checked against the settings in the product, never a customer's private conversation.

Use them as a rehearsal. Read the caller's lines in the voice of your own worst Tuesday and ask whether the assistant's reply would have satisfied you. If a line would land wrong in your trade, that's a greeting, a question or a routing rule you'd set differently, and the settings section tells you which one.

If you'd rather hear it than read it, the demo runs your own scenario in two minutes with no card, and the how-it-works page walks the same call from forwarding to transcript.