Ticket to Fin response

Great question — and this is a documented limitation in how Fin works. The Intercom Help Center confirms it directly: the "Let Fin handle" step only triggers a response after a customer sends a message. When a ticket is created via a contact form, the submission populates ticket fields (attributes/description) rather than firing as a conversational message, so Fin waits — and the ticket closes due to inactivity before the customer sends anything.

Here are a few approaches to work around this, each backed by Intercom's own documentation:

1. Add "Let Fin handle" to a Ticket Workflow (with a Send Message step first)

Per the Use Fin AI Agent in Workflows help article, Fin requires a customer message to trigger a response. The workaround is to build a Workflow triggered on "A ticket is created" (documented in Automate ticket actions using Workflows), then add a "Send a message" action to prompt the customer to reply — for example, "Thanks for submitting your request — please reply here and we'll get you an answer right away." Once the customer replies, Fin will engage via the "Let Fin handle" step. Note: the sent message itself does not trigger Fin; Fin still requires the customer to respond to that prompt.

2. Deploy Fin over email (if your tickets are email-based)

If your contact form submissions route into your email channel as inbound emails (not directly as tickets), you can enable Fin over email. The Deploy Fin AI Agent over email article covers the setup in detail — Fin will treat the inbound email itself as the triggering message and respond automatically. Note this only applies when the form generates a genuine inbound email conversation, not when it creates a ticket directly via form or API.

3. Use a "Reply to customer" action in the Workflow

In the Workflow triggered on ticket creation, add a "Reply to customer" or "Send a message" action before the "Let Fin handle" step. This sends a prompt to the customer asking them to reply, and once they do, Fin will respond. See Using actions in Workflows for the full list of available Workflow actions.

4. Start a Messenger conversation from the form (instead of a ticket)

Rather than creating a ticket directly on form submission, use the Intercom JavaScript API / GTM integration to trigger the Messenger's

Show New Message

method when the form is submitted, pre-populating the message with the form content. This opens a live Messenger conversation with the customer's query already filled in. Then set up a Workflow using the "When customer sends their first message" trigger and add a "Let Fin handle" step — Fin will respond immediately since the pre-filled message counts as the triggering customer message. This is the closest experience to an instant, seamless reply.

5. Use an outbound message + Fin follow-up

Send an outbound chat or post message to the customer after the ticket is created, and add "Let Fin respond" as a follow-up action. See Let Fin AI Agent follow up after Outbound messages or Workflows for setup details. When the customer replies to that outbound message, Fin will respond. Important caveat: in this mode Fin gives one answer and then automatically hands the conversation over to your team — even if the issue was resolved. If you want Fin to stay engaged for the full conversation, use a Workflow instead with "Conversation starter is: Outbound message" as an audience condition, then add the "Let Fin handle" step.

The core fix across all of these is the same: Fin requires a customer message to engage. Options 1, 2 and 3 work within the ticket/workflow model by prompting the customer to reply. Options 4 and 5 sidestep the ticket creation entirely by routing the customer into a Messenger or outbound conversation where Fin can respond directly.

Hope that helps — happy to walk through any of the setups in more detail!