What a connected assistant can do

A connected assistant has exactly 10 actions on your account: 7 that only read, 3 that change something. This page lists each one, what the assistant has to give it, and what comes back. You never call these yourself. You ask in plain words, and the assistant picks the action.

Every action answers only for the account you signed in with. The guest messages themselves stay in your account: no action returns audio, transcripts, phone numbers or names. The full list of what the assistant cannot do is on the setup page.

Read-only looks something up and changes nothing.Does something changes your account, and Claude and ChatGPT ask you to approve it first unless you turn that off on their side.

Reads

Search my events

Read-only

Finds your events by part of the name, a date range, or status. This is where every other question starts: the assistant looks the event up here, then uses what it finds.

What it needs

Nothing is required. Ask for all events and you get the most recent ones first.
Part of the event name, if you have one in mind.
An earliest date, a latest date, or both.
A status: draft, active or archived.
How many to return. Twenty-five by default, one hundred at most.

What comes back

For each event: name, date, status, whether it is unlocked, and the gallery link.
Whether a share code is set on the gallery (never the code itself).
Call-in on or off, with the window dates.
Message counts: total, ready, cleaning, waiting, needs attention, and hidden by you.
Plays, downloads and visitors so far, and whether the gallery was sent and opened.

Worth knowing

Only your own events. The connection is tied to the login you approved it with.
Never guest audio, transcripts, phone numbers or names.

Try asking

Which of my November events still have messages waiting?

Shown to the assistant as search_events.

Get one event

Read-only

The full status of a single event, message by message. Use it when the counts from a search are not enough and you want to know which messages are where.

What it needs

The event. The assistant finds it by name through a search first; you do not need an id.

What comes back

Everything a search returns for that event.
One line per message: its number, how it arrived (a call, a text, the web recorder or an upload), its state, its length in seconds, and whether you hid it from the gallery.
States are ready, cleaning, waiting, needs attention, or video.
A link to the event in your dashboard.

Worth knowing

Message states only. Never the audio, the words, or who left it.
Up to five hundred messages per event are listed.

Try asking

Is anything still cleaning on the Nguyen wedding?

Shown to the assistant as get_event.

Check audio status on an event

Read-only

Answers "does it have audio ready?" for one event. You get the message counts by state and a one-line list, Message 1: ready, Message 2: cleaning, and so on.

What it needs

The event. The assistant finds it by name through a search first.

What comes back

How many messages are ready, cleaning, waiting, need attention, or are video.
Whether every audio message is ready, as a plain yes or no.
One line per message with its number and state, nothing else.
A link to the event in your dashboard.

Worth knowing

States only. No file names, no audio, no words, no guest details.
Up to five hundred messages per event are listed.

Try asking

Is all the audio ready on the Okafor baby shower?

Shown to the assistant as get_event_audio_status.

List events that need a look

Read-only

Answers "is anything stuck?" across your whole account. It lists events that have a message in needs attention, or a message still cleaning more than thirty minutes after it arrived.

What it needs

Nothing is required.
How many events to check at most. Twenty-five by default, one hundred at most.

What comes back

For each event: name, date, how many messages need attention, how many look stuck, and a link to it in your dashboard.
An empty list with a note when nothing needs you.

Worth knowing

Needs attention means a message that failed, was too short, was too large, or was an unsupported file. Those never reach the gallery until you deal with them.
Stuck is measured from when the message arrived, so a re-clean you start on an older message can show as stuck for its first thirty minutes. Check the event page before worrying.

Try asking

Is anything stuck on my events this week?

Shown to the assistant as list_events_needing_attention.

Get the gallery link

Read-only

Hands the assistant the share link for one gallery so it can put it in a message or email you are drafting elsewhere.

What it needs

The event.

What comes back

The gallery link. Your own domain when it is verified, otherwise the Happy Hear Audio one.
Whether guests need a share code to open it.
Status, whether the event is unlocked, whether the gallery was already sent, and whether downloads are on.

Worth knowing

Never the share code itself. If one is set, the assistant is told guests need it and that it lives only in your dashboard.
This does not send anything. Sending the gallery to your client still happens from the event page.

Try asking

What is the gallery link for the Nguyen wedding?

Shown to the assistant as get_gallery_link.

Get gallery stats

Read-only

Answers "how many people listened?" for one event, from the same numbers the event page shows.

What it needs

The event.

What comes back

Visitors, plays and downloads so far.
Whether the gallery was sent, and the date it was first opened.
A link to the event in your dashboard.

Worth knowing

Counts and dates only. Never who visited, where from, or which message they played.

Try asking

How many people have listened to the Rivera 50th gallery?

Shown to the assistant as get_gallery_stats.

Get my plan and usage

Read-only

Tells the assistant which plan your account is on and where you stand with it, so it can answer "do I need to pay for this next event?" without guessing.

What it needs

Nothing.

What comes back

Your plan: per event, monthly or annual, and whether unlimited events are included right now.
Subscription status and the date it is paid through or renews. For a paused subscription, when the pause ends.
Whether your free first event has been used, when your first event was created, and how many events you have.
A link to your settings page for billing.

Worth knowing

No card numbers, invoices or payment details. Billing changes happen in your settings page, never through an assistant.
The event count is events that exist today. Deleted events are not counted.

Try asking

Am I still on the free event, or do I need to pay for the next one?

Shown to the assistant as get_plan_and_usage.

Changes

Start cleaning an event

Does something

Runs Clean All on an event you own: audio cleaning starts for every message that has not been cleaned yet, exactly as the button on the event page does.

What it needs

The event.

What comes back

How many messages started, how many are queued behind them, and how many were already clean.
Or, if a clean is already running on that event, a note saying so.

Worth knowing

Real processing starts, and it is billed the same way as the Clean All button. The event has to be unlocked first; a locked event answers with that message instead.
Safe to ask twice. A second request never starts a second run and never re-cleans a finished message.
Cleaning takes a few minutes per message and finishes in the background. Ask about the event again for progress.
Daily limit: 30 cleaning requests per account in any 24 hours, the same on every plan. Past that, nothing changes and the assistant is told to use the dashboard or ask again tomorrow.

Try asking

Start Clean All on the Rivera 50th.

Shown to the assistant as start_cleaning.

Create an event

Does something

Creates a new event in your account with a name and, if you give one, a date. The same rules as the dashboard apply: the free first event, a subscription, or otherwise the event is created locked and waits for payment.

What it needs

An event name, up to 120 characters.
An event date, if you know it yet. Day, month and year.

What comes back

The new event and a link to it in your dashboard.
Whether it is unlocked, and whether it needs payment before it can be used.
If your free event is being reviewed, a note saying the dashboard shows the next step.

Worth knowing

This adds a real event to your account. A locked event is not charged; payment happens in the dashboard, never through the assistant.
Nothing else is set here. Branding, player style, call-in and sharing are set up in the dashboard as usual.
Daily limit: 10 new events per account in any 24 hours, the same on every plan. Past that, nothing is created and the assistant is told to use the dashboard or ask again tomorrow.

Try asking

Create an event called Rivera 50th on November 14.

Shown to the assistant as create_event.

Update event name or date

Does something

Changes the name of an event, its date, or both. Nothing else about the event can be changed this way.

What it needs

The event.
A new name, a new date, or both. The date can also be cleared.

What comes back

Confirmation that it was updated, with a link to the event in your dashboard.

Worth knowing

Moving the date moves the call-in window the same way the dashboard does.
Branding, player style, call-in dates on their own, sharing settings and everything else stay as they are.
Daily limit: 50 event edits per account in any 24 hours, the same on every plan. Past that, nothing changes and the assistant is told to use the dashboard or ask again tomorrow.

Try asking

Move the Patel reception to December 6.

Shown to the assistant as update_event.

Not on this list

If something is not on this page, the assistant cannot do it. Deleting an event or a message, changing branding or player style, moving a call-in window on its own, sharing settings, downloads and payment all stay in your dashboard. Each action an assistant takes is logged with your account, the action, the event it touched and the time.

Back to Connect an AI assistant Back to Help Center