Forms — In a regular form, the answer becomes a row in a spreadsheet. At Olie, it becomes action.
In Google Forms or Microsoft Forms, each answer sits in a spreadsheet, waiting for someone to read it or another app to act. At Olie, the answer to any field, in any form, already classifies the request, chooses who executes it and puts people, AI agents and systems to work.
The same answer, two destinations. See what happens in each one.
Someone answers a workshop screening form: a company with 16 to 30 employees, pain in processes. On one side, the regular form. On the other, Olie.
Regular form
| Timestamp | Name | Employees | Pain |
|---|---|---|---|
| 09/29 09:15 | Paula Nogueira | 16 to 30 | Processes |
1 answer in the spreadsheet. Nobody has been notified for 0 s.
- Someone needs to open the spreadsheet
- Another app to notify the team
- Another one to send the WhatsApp
- Another one to create the task in the system
Olie form
- Answer receivedThe card is born in the funnel with all the answers.0 s
- ClassifiedMid-sized company · Pain: Processes · High priority2 s
- Distributed to two funnelsSales (consultant Mateus) and Diagnosis (workshop material)3 s
- WhatsApp sent"Hi, Paula! I saw your pain is in processes. Can I show you a case?"6 s
- AI agent read the answerSummarized the pain described and prepared the diagnosis questions.11 s
Change one answer. Watch the operation change course.
Choose the form answers. The rule your company wrote decides, right away, how to classify, who to send it to and how the execution happens.
How many employees?
What pain do you want to solve?
Satisfied with the workshop?
- Sales funnelConsultant Mateus
- Diagnosis funnelWorkshop material on processes
Illustrative example. The rules are built by your company, without coding.
Four ways to use it. The same power in all of them.
A request catalog for those inside the company, a link for those outside, the information the card needs to move forward and an editor to create all of it without coding.
Each role sees its own catalog. Whoever requests doesn't enter the funnel of whoever executes: the request arrives as a card, at the right step.
Each answered field can trigger an action. Without another app in between.
When a field's value changes, Olie's automation kicks in. And AI agents look up any answer in any form to decide the next step.
- WhatsApp messageThe conversation starts seconds after the answer.
- EmailTo the customer, to the manager or to the address that came in the form.
- AI agentReads the answers, summarizes, qualifies and moves the card.
- API and webhookNotifies your system: SMS, phone call, ERP or whatever your company uses.
- Another formOne form's answer pulls up the next: inspection, contract, survey.
- Move and distributePuts the card at the right step and funnel, in more than one if needed.
- Tag and priorityThe customer type and urgency show up on the card.
- Spreadsheet, if you wantEvery form exports. The difference is that nobody depends on it.
What is the difference between the Olie form and Google Forms or Microsoft Forms?
Google Forms and Microsoft Forms store the answers in a spreadsheet. For someone to act, they need to read the spreadsheet or connect other apps. At Olie, the form is inside the process: each answer creates or updates a card in the funnel, and any field can trigger an automation, a WhatsApp message, an email, an AI agent or a webhook to another system. The same answer classifies the request, distributes it to the right people or funnels and defines whether the execution is sequential, parallel or hybrid across people, AI and integrations.
Questions about forms
Does whoever answers the public form need an Olie login?
No. The published form lives at an open link, which can go in the ad, the website, the landing page or the intranet. You can set a start and end date, change the color and send the person to another page after they answer.
How does the internal request catalog work?
Each role sees its own catalog: the director sees travel and purchases, the salesperson sees reimbursement, operations sees material requests. Whoever requests doesn't need to enter the funnel of whoever executes: the request arrives as a card at the right step.
Can the form block the card from moving forward?
Yes. With a required field or a checklist at the step, the card only moves forward once the information is filled in. Not even the administrator skips it.
Do AI agents read the answers?
Yes. The agent looks up and answers the project's forms, and uses those answers to summarize, qualify, decide and move the card.
What types of questions can I create?
There are 21 field types: text, number, currency, counter, date and time, selection, checkbox, matrix, email, phone, link, attachments and fields linked to customer, contact, user and project. Fields can appear or disappear based on the previous answer.
Updated on · Source: docs.olie.ai
Eliminate internal emails. Start executing.
Use the dynamic internal request catalog: each menu changes with the person's position.
The request distributes the work to the right funnels, each funnel with its owners, each step with a deadline to execute.