Submit-Info
Submit-Info turns a list of questions into a form your customers and field staff fill in on WhatsApp or on a web page, and brings every answer to a shared inbox your team works through and your systems can read.
Four sample forms, as a person sees them on the web page. Fill one in. It is a demo: nothing is uploaded and nothing is sent.
On WhatsApp the same questions open as a form inside the chat, drawn in WhatsApp's own style.
One screen: a number, a photo, done.
This form is nothing more than this list
Step 1: Your reading
* shown only when an earlier answer asks for it. Adding a question is adding a row.
Step 1
Write your questions as a plain list, or start from a template. There is nothing to draw and nothing to code.
Step 2
One button turns the list into a form inside WhatsApp and a web page with the same steps. Share a word, a link or a QR code.
Step 3
Customers or your own field staff fill it in, add photos, files or a location, and get a reference straight away.
Step 4
Each submission lands in a shared inbox and moves through your stages. Assign it, add a note, reply, approve.
Step 5
Automations reply, e-mail and call your own software. Every change also goes to your webhooks.
Each of these comes as a template: a form, its stages and its automations. Install one, then change anything.
Customers say what they need and add photos. You send the price with Accept and Decline buttons, and a reminder if they do not answer.
Applicants send their details and documents. Managers approve or decline with a note, and the applicant is told at each stage.
Ask for each document you need. Mark what arrived as received, verified or incomplete, and ask again for what is missing.
A reading and a photo of the meter. Usage is worked out from the last reading, and a reading that looks wrong is set aside for a check.
Category, description, photo and location. Urgent reports alert the team, and the reporter hears back at each stage.
Field staff close a job from their phone: work done, parts, time, photos, location. Ready to pass on to your dispatch system.
Delivery number, who received it, a photo and the location. A problem tick moves it to its own stage and alerts the team.
Amount, category, date and a photo of the receipt. Managers approve or reject, and the sender is told.
Contact request, complaint, inspection checklist, incident report, maintenance request, leave request, feedback survey.
A submission is not an e-mail that gets lost. It has a reference, a stage, an owner and a history of everything that happened to it.
Everything that was sent, in one place: as a list, as a table with a column for every question, or as a board with a column for every stage. Search, filter, save a view, export to CSV, Excel, JSON or PDF.
New, In review, Approved, or whatever your work is called. A stage can be kept for managers, can ask for a note, and can send its own message to the person who sent the form.
Admin, Manager, Agent and Viewer are starting points. Each ability, such as replying, changing a stage, exporting or deleting, can be switched on or off for one person.
Limit a team member to some forms, or to what is assigned to them, and hide contact details where they are not needed. Invited staff use a light app of their own and never see the rest of your account.
An automation is a sentence: when this happens, if this is true, do that. One of the things it can do is call your own software, with the answers filled in.
Every submission event (created, updated, stage changed, assigned, replied) goes to the webhooks of your account. There is nothing to set up for it.
Give an address and how to sign in. An action names the method, the path and a JSON body, each filled with values from the submission.
Point to an OpenAPI 3 document in JSON. Its operations become a list to pick from, and you fill in the parameters of the one you choose.
Give the address of an MCP server and its token. Its tools become a list to pick from, and you fill in the arguments.
Before anything is switched on you can try an action with a real submission and see the request that would be sent and the answer that came back. Every run is logged step by step, and a call that fails is tried again.
Everything a person can set up in the dashboard, a program can set up through the API. One guide describes every question type, trigger, action and placeholder, and one call applies a whole solution, or only checks it and lists what to fix.
GET /v1/{number}/submit/guide the whole vocabulary, with worked examples
POST /v1/{number}/submit/setup forms, lists, automations and connections in one document
POST /v1/{number}/submit/forms/{key}/publish The same routes are tools on app2email's MCP server, so an assistant such as Claude or ChatGPT can read the guide, build the forms and the automations, and publish them. How an agent sets it up.
Connect your WhatsApp number, pick a template or write your own questions, and publish. In your dashboard it is under Integrations, Submit-Info.