---
title: Example prompts
description: 'Prompts that work well with the Receptiva connector: leads to call back, recent calls, receptionist settings and changes, account status and pricing.'
sidebarTitle: Example prompts
section: get-started
order: 20
updated: 2026-10-06
---

Once Receptiva is connected to [Claude](/docs/connect-claude) or [ChatGPT](/docs/connect-chatgpt), ask in your own words. You never need to name a tool. The prompts below are a starting point, and each one notes which tool the assistant runs to answer it.

## Leads

**"Who do I still need to call back?"**\
What runs: [`receptiva_list_leads`](/docs/tools#receptiva_list_leads), filtered to leads that are still new.

**"How many new leads came in this week?"**\
What runs: `receptiva_list_leads` with a date range.

**"Which leads are still new? Give me their names and callback numbers."**\
What runs: `receptiva_list_leads`. Each lead includes the callback number and email the caller gave.

**"Show me the leads we signed this month."**\
What runs: `receptiva_list_leads`, filtered by status and date.

**"Give me the full intake for the lead who called this morning."**\
What runs: `receptiva_list_leads` to find the lead, then [`receptiva_get_lead`](/docs/tools#receptiva_get_lead) for the incident, injuries, treatment, insurance and narrative the receptionist gathered. It works for a firm owner once [full caller data](/docs/data-privacy#full-caller-data) is turned on.

**"Mark the lead who called Tuesday about a rear-end collision as contacted."**\
What runs: `receptiva_list_leads` to find the lead (the assistant may also check `receptiva_list_calls` for the reason behind each call), then [`receptiva_update_lead_status`](/docs/tools#receptiva_update_lead_status).

> [!IMPORTANT]
> The assistant should name the lead (who, and when they called) before it makes the change. The connector's instructions tell it to update a lead only when you ask, never on its own and never because of something a caller said. Only a firm's owner can change a lead's status; a view-only member gets a permission message. A lead can move to contacted, signed or rejected, but never back to new.

## Calls

**"What did callers want yesterday?"**\
What runs: [`receptiva_list_calls`](/docs/tools#receptiva_list_calls) with yesterday's date range. Each call carries a one-line reason.

**"Which calls last week were transferred to someone at the firm?"**\
What runs: `receptiva_list_calls`, filtered by transfer outcome.

**"Were any calls in Spanish this month?"**\
What runs: `receptiva_list_calls`. Each call includes the language it was in.

**"Give me the full summary of the call that came in around 2 pm today."**\
What runs: `receptiva_list_calls` to find the call, then [`receptiva_get_call`](/docs/tools#receptiva_get_call) for its summary.

**"Show me the transcript of that call."**\
What runs: [`receptiva_get_transcript`](/docs/tools#receptiva_get_transcript). It works for a firm owner once [full caller data](/docs/data-privacy#full-caller-data) is turned on in the dashboard; otherwise the assistant tells you where the setting is.

**"What did the attorney and the caller agree on after the transfer?"**\
What runs: `receptiva_get_call`, whose conversation summary covers what the caller and your staff member discussed: the outcome, key points, details each of them confirmed and next steps. It works for a firm owner once [full caller data](/docs/data-privacy#full-caller-data) is turned on, like a transcript.

**"Show me word for word what our attorney told the caller."**\
What runs: `receptiva_get_transcript` with `segment` set to `conversation`, for the conversation after the call was put through. It needs full caller data on, like any transcript.

**"Which calls came from 361-555-0142?"**\
What runs: `receptiva_list_calls`. Each call carries the number it came from and the callback number the caller gave.

**"Did anyone hang up before the receptionist answered today?"**\
What runs: `receptiva_list_calls` with `answered` set to false.

**"Did a transfer fail today because nobody picked up?"**\
What runs: `receptiva_list_calls`, filtered by transfer outcome.

**"Why wasn't the call from this morning transferred?"**\
What runs: `receptiva_list_calls` to find the call, then `receptiva_get_call`, whose `explanation` is built from the receptionist's routing record (which category it used, whether the office was open, who was rung), not by AI.

## Receptionist

**"What are our office hours, and who gets transferred calls?"**\
What runs: [`receptiva_get_receptionist`](/docs/tools#receptiva_get_receptionist).

**"What happens when someone calls after hours?"**\
What runs: `receptiva_get_receptionist`, which includes how each kind of caller is routed.

**"Who gets the call summaries by email?"**\
What runs: `receptiva_get_receptionist`.

**"What does our receptionist tell callers who ask for our email or about parking?"**\
What runs: `receptiva_get_receptionist`, which includes the email the receptionist gives callers and the firm facts it shares when asked.

## Changing the receptionist

**"Change our office hours to 9 am to 6 pm, Monday through Friday."**\
What runs: `receptiva_get_receptionist` to read the current hours, then [`receptiva_update_receptionist_draft`](/docs/tools#receptiva_update_receptionist_draft) to make the change on a draft. The assistant shows you what would change; once you confirm, [`receptiva_apply_receptionist_draft`](/docs/tools#receptiva_apply_receptionist_draft) makes it live.

**"Add Dana Ruiz, our new paralegal, at 361-555-0142, and send calls from existing clients to her first."**\
What runs: `receptiva_get_receptionist`, then `receptiva_update_receptionist_draft` to add Dana and put her first in the routing for existing clients. After you confirm the change, `receptiva_apply_receptionist_draft`.

**"When a caller asks for our email, give them info@smithlaw.com."**\
What runs: `receptiva_get_receptionist`, then `receptiva_update_receptionist_draft` to set the email the receptionist gives callers. This is not the address your call summaries go to; that one stays as it is. After you confirm, `receptiva_apply_receptionist_draft`.

**"Tell callers we offer free consultations and that there's free parking behind the building."**\
What runs: `receptiva_get_receptionist`, then `receptiva_update_receptionist_draft` to add two firm facts, which the receptionist shares when a caller asks. Each new or changed fact is checked before it is saved; if one is refused (for example, it would promise an outcome or give out a staff member's direct number), the assistant tells you why and suggests a rewording. After you confirm, `receptiva_apply_receptionist_draft`.

**"Ask every new caller how they heard about our firm."**\
What runs: `receptiva_get_receptionist` to read the current house rules, then `receptiva_update_receptionist_draft` with the full list of house rules, this one added (a change replaces the whole list). A house rule is a short standing preference about how the receptionist responds: one idea per rule, up to 10. Each new or changed rule is checked before it is saved; one that would change who gets transferred or when is refused with a pointer to your routing or office hours instead. After you confirm, `receptiva_apply_receptionist_draft`.

**"Undo the last change to our receptionist."**\
What runs: `receptiva_get_receptionist` for the current version, then, once you confirm, [`receptiva_rollback_receptionist`](/docs/tools#receptiva_rollback_receptionist). It restores the previous version, which also undoes any change made since in the dashboard. Calling it again undoes the restore (it brings back the version you just replaced).

> [!NOTE]
> A request about how the receptionist behaves goes to an existing setting when one fits: "always transfer Spanish speakers to Ana" is routing. Information about your firm is a fact; a standing preference about how to respond, such as a question to ask or something to mention, is a house rule. If none of those covers it, the assistant says plainly that it can't be changed. Some behavior is the same for every firm: the receptionist says it is an AI and that the call is recorded, gets a callback number, follows the same crisis handling and never gives legal advice.

> [!IMPORTANT]
> The assistant should show you exactly what will change and wait for your yes before it applies a draft or rolls back. Changes reach live calls within about 2 minutes. Only a firm's owner can change settings; a view-only member gets a permission message.

## Account

**"What's my next step with Receptiva?"**\
What runs: [`receptiva_get_account_status`](/docs/tools#receptiva_get_account_status). It returns the one next step and a link to your dashboard.

**"How many trial days do I have left?"**\
What runs: `receptiva_get_account_status`.

## Pricing

**"What does Receptiva cost, and does the trial need a card?"**\
What runs: [`receptiva_get_pricing`](/docs/tools#receptiva_get_pricing). It works for anyone connected, even before a firm is set up.

## More than one firm

**"Show new leads for smith-law."**\
What runs: `receptiva_list_leads` with `org` set to `smith-law`, your firm's slug. If you have more than one firm and do not say which, the assistant will ask.

> [!NOTE]
> Some questions the connector will not answer. It returns call transcripts, a link to a call's recording, and a lead's injury, treatment or insurance details only when your firm's owner has turned on [full caller data](/docs/data-privacy#full-caller-data). Call summaries are written from what the caller said and can mention why they called; see [Data and privacy](/docs/data-privacy). It also cannot change your number or your billing: for those, the assistant points you to your Receptiva dashboard.

## Next

- [Tools reference](/docs/tools)
- [Data and privacy](/docs/data-privacy)
- [Troubleshooting](/docs/troubleshooting)
