AddThisFeature

AI Reply Suggestions

Offer a few short reply options that fit the current message or thread.

moderate AI Content

What it adds

A small set of one-tap reply drafts generated from the visible thread, inserted into the composer for editing before sending.

What your agent is told to do

5
  1. 1

    Generate suggestions from the visible thread only, and only when the last message is from someone other than the user. Suggesting a reply to the user's own message is noise.

  2. 2

    Insert the chosen suggestion into the composer as editable text. Do not send on tap, however short the reply, because a one-tap send makes every model error a message the user cannot recall.

  3. 3

    Require the options to differ in intent, not in wording — for example accept, decline, and ask for more detail. Three paraphrases of the same sentence give the user nothing to choose between.

  4. 4

    Recompute or clear suggestions when a new message arrives in the thread, so the user is never offered a reply to a message that has already been superseded.

  5. 5

    Long-form composition from a record belongs to AI Email Drafting; this feature owns short in-thread responses. Reuse that feature's context allow-list rather than defining a second one.

Edge cases it handles

8
  • Distinct intent is the whole value. If the model returns options that are substantially the same, drop the duplicates and show fewer rather than padding the list.
  • A suggestion must not commit the user to a delivery date, a refund, a discount, or an escalation the user has no authority to grant. Keep suggested commitments vague enough to be safe or omit them.
  • Tone must follow the thread and the relationship. A breezy suggestion under a complaint, or a formal one in a running internal chat, reads worse than no suggestion at all.
  • Internal comments, private notes, and messages from participants the current user cannot see must be excluded from the context, even when they sit in the same thread record.
  • Stale suggestions are actively harmful. Clear them when the thread changes, when the composer already has typed text, and when the user switches threads.
  • A refusal, a timeout, or malformed output must result in no suggestions and an unchanged composer, never an empty chip row or a placeholder the user can tap.
  • Suggestions fire on every thread view, so cost accumulates quietly. Generate lazily on user intent or on thread open at most once, and cache against the thread's last message.
  • With the model unavailable the composer must behave exactly as before, with the suggestion row absent rather than showing a persistent error.

Definition of done

9
  • Suggestions appear only when the latest message is from another participant.
  • Choosing a suggestion inserts editable text and never sends the message.
  • The offered options differ in intent, and near-duplicates are removed.
  • Suggestions are cleared or regenerated when the thread receives a new message.
  • Context excludes internal notes and any message the current user cannot access.
  • Generation is cached per thread state and capped per account.
  • Model failure leaves the composer fully usable with no suggestion row.
  • The feature matches the existing design system.
  • No existing functionality is broken.

Related features

How it works

  1. 1

    Copy the link

    Grab the Markdown instruction URL for this feature.

  2. 2

    Give it to your AI

    Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.

  3. 3

    It inspects, then implements

    Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.