Submissions

Open Autoreply → Submission.

What this page is for

Submission forms collect structured answers inside WhatsApp (and other messaging channels when linked from autoreply). You define questions here, then start a form from an Autoreply template with response type Submission.

Review completed and in-progress sessions on Answer — the button at the top of this page opens Autoreply → Submission → Answer (same feature, session list view).

Sample data shown.

End-to-end workflow

1. Create a form on Autoreply → Submission (questions, messages, optional notify).
2. Link it from Autoreply — response type Submission, pick the form, link devices.
3. Set device mode — On incoming message → Autoreply on each linked device.
4. User triggers the form — sends a keyword that matches your autoreply template.
5. Kirisan runs the chat session — opening message, questions one by one, optional review, closing message.
6. Review on Answer — filter sessions, open View for question-by-question answers.

---

Submission list

Column / control	What it does
Answer	Opens the session list for all forms.
New submission	Create a form.
Name	Form title shown in the autoreply picker and on Answer.
Questions	Click N steps to preview question text and attachments.
Internal note	Private note for your team (not sent to users).
Actions	Edit submission or Delete submission.

---

Create or edit a form

Click New submission or edit a row.

Sample data shown.

Questions

1. Enter Question text for each step.
2. Optionally attach a file per question (upload or Pick from Files) — images, PDF, Office docs, or TXT up to 10 MB.
3. Click Add question for more steps.

Kirisan asks questions one at a time in the order shown. The user’s reply to each message becomes the answer for that step (text or media).

Flow messages

Field	Purpose
Opening message	Sent once when the form starts (before question 1).
Closing message	Sent after the user confirms with /done (when review is on) or immediately after the last answer (when review is off).
Cancel message	Sent when the user types /cancel or the session expires.
Review step	When enabled, shows a numbered summary so the user can fix answers before submitting.
Review message	Text shown with the summary. Use [[review]] where the numbered answers should appear (see Variables).

Contacts (optional)

When someone completes the form, Kirisan can save them as a contact (if new) and add them to a Contact → Groups group you pick here. Leave as None to skip.

Notify when complete (optional)

After the user finishes (sends /done when review is on, or after the last answer when review is off), Kirisan can send a text summary to up to 5 destinations:

Field	Purpose
Channel	WhatsApp or Email.
WhatsApp number(s)	One or more numbers, comma-separated (for example 081234567890, 081298765432).
Email address(es)	One or more addresses, comma-separated.

Click Add destination for each row. For server-to-server delivery instead, add a webhook with the submission event.

Internal note

Optional team-only note — shown in the submission list, never sent to the user.

Click Save to store the form.

Built-in chat commands

These work during an active submission session (case-insensitive):

Command	When
/cancel	Abandon the form anytime.
/done	Submit answers — only when Review step is on, after the summary.
1, 2, …	During review only — jump to that question to replace an answer.

Mention these in your opening or review message if you want users to know about them — Kirisan does not add them automatically.

---

Connect a form to autoreply

1. Save the submission form on this page.
2. Open Autoreply → Autoreply and create or edit a template.
3. Set Response type to Submission and pick this form.
4. Link the template to your device(s).
5. On each device, set On incoming message to Autoreply under Channel → channel → Devices.

When a user sends a matching keyword, the form session starts. Only one active submission session runs per sender per device at a time.

---

Answer — review sessions

Open Answer from the Submission page (or go to the session list after clicking Answer).

Sample data shown.

Filters

Control	What it does
Submission ID	Limit to one form — enter the numeric ID shown under the form name (for example #12). Leave empty for all forms.
Status	Filter by session state (see table below).
Apply	Reload the table with your filters.

Session table

Column	What it shows
ID	Unique session identifier.
Form	Form name and submission ID (#…).
Device	WhatsApp line or bot that handled the chat.
Sender	User phone or chat ID.
Status	Current session state.
Started	When the session began.
View	Open question-by-question answers.

Pagination appears at the bottom when there are more rows than one page.

Session statuses

Status	Meaning
active	User is answering questions (not yet finished).
review	User is on the review summary (review step enabled).
editing	User picked a question number to change an answer during review.
completed	Form finished — answers are final.
cancelled	User sent /cancel or abandoned the session.
expired	Session timed out before completion.

Session detail

Click View on any row.

Sample data shown.

The popup shows:

• Form name and ID
• Status, Device, and Sender
• Each question with the user’s Answer (plain text and [attachment] links for uploads)

Use this to verify registrations, support intakes, or survey responses without opening the channel inbox.

---

Webhooks and exports

Submission events can fire webhooks:

Event	When
submission	When the user completes the form (final answers included).

Legacy endpoints may still use the alias submission.completed — new webhooks should use submission only.

Pair with Notify when complete on the form for human alerts, or webhooks for CRM automation.

There is no CSV export on Answer today — copy from Session detail or consume webhook payloads for bulk export.

---

Privacy

Only collect data you need. Tell users what you store, especially on WhatsApp and Telegram where session trust matters.

---

Related

• Autoreply — keyword triggers that start a submission
• Flow — alternative multi-step automation on a canvas
• Webhooks — real-time submission events
• Variables — [[review]] and other tokens in review messages