Next step buttons

Next Step Buttons

End useful responses with practical suggested next actions when they help the user keep moving.

Core Rule

When there are real actionable suggested next steps, include both:

1. A Suggested next list in the message body with enough context.
2. Matching short action buttons when the channel supports clickable controls.

If buttons are unavailable or degrade, the text list is the complete fallback.

When To Use

Use after:

• event, travel, market, or research scans
• background agent status or result updates
• task completion summaries
• decision briefs with several paths
• inbox or calendar triage
• multi-step workflows where the next prompt is predictable

Skip when:

• the user asked a tiny factual question
• the response is purely explanatory and has no real next action
• there is one obvious safe next step that should be done directly
• choices would be fake, noisy, or decorative

Output Shape

Use this structure at the end of the response:

Suggested next:

• Action title — One sentence explaining what this does or why it matters.
• Action title — One sentence explaining the outcome or tradeoff.
• Action title — One sentence explaining another useful path.

Then, for channels that support buttons, send matching buttons with short labels.

Button Label Rules

Good labels are:

• action-oriented
• short enough to scan
• contextual without needing A/B/C prefixes
• aligned with the matching list item

Examples:

• Build schedule
• Check signups
• Prep networking
• Draft reply
• Assign agent
• Review findings
• Open schedule

Avoid:

• Continue
• Learn more
• Option A
• Do it
• long sentence labels

Description Rules

Put detail in the list, not the button.

Example:

Suggested next:

• Check signups — Verify which AI Week events are still open, invite-only, paid, or closed.

Button label:

• Check signups

Safety Rules

Buttons must not silently perform sensitive, irreversible, or external actions.

Safe button actions:

• Draft email
• Preview reply
• Check registration
• Build itinerary
• Prepare checklist
• Assign agent
• Open link

Needs explicit confirmation:

• Send email
• Register or pay
• Book travel
• Post publicly
• Delete data
• Message someone else

Channel Behavior

Telegram:

• Use message body list plus button payloads for actionable suggested next steps.
• Keep labels short and contextual.
• If rich controls degrade, the text list is enough.

Other channels:

• Use a compact text list unless clickable controls are supported.

Example

Response body:

AI Week has a lot of overlap. I would prioritize builder/community sessions over generic mixers.

Suggested next:

• Build schedule — Turn the shortlist into a realistic day-by-day plan.
• Check signups — Verify which events are still open or invite-only.
• Prep networking — Make a lightweight plan for who to meet and what to say.

Buttons:

• Build schedule
• Check signups
• Prep networking