Skip to Content
TicketsIntake Methods

The 4 Ticket Intake Methods

Loopwave can open tickets four different ways, from a deliberate agent action to a hands-off public form. Mix and match them to fit your support process.

1. Agent convert

An agent turns a live chat into a ticket. Manual and precise.

2. Keyword auto-create

A ticket opens automatically when an inbound message contains a keyword.

3. Every new chat

A ticket opens automatically the first time any new conversation starts.

4. Public intake form

Anyone can submit a request through a hosted form, no login required.

1. Agent convert (from a chat)

An agent creates a ticket directly from a conversation. The customer’s name and phone are pulled from the chat, and the ticket is tagged chat. This is the manual, on-demand path — full walkthrough in Create from a chat.

2. Keyword auto-create

When enabled, Loopwave watches inbound messages and opens a ticket automatically if the message text contains one of your configured keywords.

SettingDefaultNotes
EnabledoffTurn on keyword intake.
Keywordssupport, help, refundCase-insensitive substring match. Up to 50.
Cooldown (minutes)60One auto-ticket per chat per window (0–10080).
  • The ticket subject becomes WhatsApp: <first 80 characters of the message>.
  • The ticket is tagged keyword, priority med, with the customer’s name and phone filled in from the chat.
  • Messages your team sends and group chats are ignored.

The cooldown prevents a chatty customer from spawning a stack of tickets. Within the cooldown window, repeated keyword hits from the same chat won’t open new tickets.

3. Every new chat

When enabled, Loopwave opens a ticket the first time it ever sees an inbound message from a given conversation — useful when every new customer should become a tracked record.

SettingDefaultNotes
EnabledoffTurn on new-chat intake.
Cooldown (minutes)60Shared with keyword intake.
  • The subject is New conversation (or New conversation with <name> when a name is known), tagged new-chat, priority med.
  • Outbound messages and group chats are ignored.

4. Public intake form

Loopwave hosts a no-login intake form so customers can submit a request directly. It behaves like a help-desk contact form and creates a ticket on submit.

FieldRules
Name1–120 characters
Phone3–40 characters
Subject1–200 characters
MessageOptional, up to 2000 characters
  • Submissions create a ticket tagged form at priority med.
  • The form is rate-limited to 10 submissions per minute per IP to deter abuse.
  • The response only returns the ticket reference — internal IDs are never exposed.
  • The form can be turned off; when disabled, submissions are rejected.

The public form is the only intake path that doesn’t require a login. Keep it enabled only while you want to accept public submissions, and rely on the built-in rate limit to blunt spam.

Configuring intake

Keyword, new-chat, and form settings live together in your ticket intake settings (admin-only to change; any signed-in user can read them). Changes take effect within about 30 seconds as Loopwave refreshes its cached settings.

Work the board

See how tickets flow across statuses and priorities.