How to set up conversation goals

After the agent answers a question it can append one nudge toward a goal — at most once per person in any 24 hours. It sends the copy you configure here; it never composes a new one at send time.

Business objectives are separate from What the agent handles on the Voice tab (those conversational rules shape the answer; these add a nudge after it has been given).

Before you start

• Conversation goals are available on all plans with an active AI assistant.
• Only an owner or admin can save goals.
• The agent has to be answering for a nudge to be sent — see Set up the AI sales agent.

The three goals

Set one up

1. Go to Agent → Goals.
2. Toggle the objective on.
3. Fill in its field — the URL for Share a link, the field key for Capture a lead.
4. Write the Nudge message, or click Draft with AI to have one written for you. The draft lands in the box; it is not saved and nothing is sent until you review it and click Save.
5. For Capture a lead, choose When the email lands, then…:
   • Nothing more (just save it)
   • Send a follow-up message — and write it
   • Hand the thread to a human
6. Click Save objectives. They take effect as soon as they are saved — unlike the voice, objectives are not part of the revision you activate in Overview.

The confirmation the agent sends after an email lands is the Lead-capture confirmation field on the Voice tab — blank uses the built-in default.

Check it

In Agent → AI Playground the nudge is not appended (the Playground never sends links or cards). To see it for real, DM your connected account from a second Instagram account with a question the agent can answer; the nudge follows the answer in that thread and in your Inbox.

Common problems

The nudge did not appear. It sends at most once per person in any 24 hours, only after the agent answered, and only when that goal is on and saved.

I want the nudge on every message. That is not offered: one per person in 24 hours keeps it from reading as spam.

The email was captured but I want it in a custom field. Change the field key on Capture a lead; create the field first under Contacts → Custom fields.

Full reference: The AI agent.

When a capture ask or save needs recovery

A capture ask owns the next reply only after its own confirmed send. HyperDM keeps that ask's exact field and identity across retries; changing a configured goal does not silently reinterpret an already delivered ask. A captured confirmation follows real typed storage, not an attempted save. If storage is temporarily unavailable, the same inbound can recover without declaring it captured or asking again under a new identity. An optional ask that could not be delivered does not consume a customer's real question, and a confirmed promised link remains delivered even if that optional ask fails. Goal end actions keep their existing best-effort behavior.