Forms walkthrough

A full guided tour of the form builder - templates, questions, logic, endings, design, responses and settings.

This is the companion guide to the Forms walkthrough video. It follows the same order as the video, so you can read it start to finish or jump to the section you need. You can open the same video inside the app from Forms → Open tutorial.

Forms exist for one reason: to get the highest possible conversion rate when you are running ads and funnels. The builder has been iterated on across a very large amount of live ad spend, and every setting below exists because it moved the numbers.

Things to be aware of

Read these first. They are the handful of mistakes that cause almost every "my form isn't working" report.

Every path must reach an ending. If your logic rules don't send a respondent to an ending screen, they can finish the questions with nowhere to go - and no submission, no contact, no lead. The builder shows a logic warning banner when an ending is unreachable or a path dead-ends. Do not publish until every warning is resolved.
The first ending is the fallback. Anyone who isn't routed by a logic rule lands on the first ending in the list. Keep it as your main "thank you" screen and make sure it creates the contact and pipeline lead.
"Add respondent as a contact & pipeline lead" is ON by default on every ending. Turn it OFF on disqualifier endings, or people you meant to filter out become leads - and can trigger lead_created automations (calls, texts, emails) you never intended to send.
Turn on partial capture. Without "Save contact at this point" or "Capture partial response here", anyone who abandons the form leaves nothing behind. With it, you keep the answers given so far and can follow up.
Publishing matters. Editing the form does not change the live version - click Push to Live after making changes, or your embedded/shared form keeps showing the old one.
Import from URL does not carry conditional logic. Public form links only expose the questions, so branching must be rebuilt in Myra. Migrating from Typeform? Use the Typeform integration instead - it pulls logic and historic responses too.
Verification is charged per check. Email and phone verification block fake submissions before they cost you a call, and each verified submission incurs the per-check fee shown next to the toggle. That is the cost of never dialling a fake number.

Starting a form

On the Forms page you have four ways to begin:

Templates - a library of ready-made forms. Pick the closest one and edit it, or hand it to Build with AI and describe the changes you want.
Recommended templates - our standard, proven layouts, including the Live Transfer form.
Import from URL - paste a public link to an existing form (Typeform, Tally, Jotform, Google Forms and similar) and Myra pulls the questions across. Conditional logic usually cannot be read from a public URL, so expect to rebuild the branching in Myra. This is the option for platforms we do not integrate with directly.
Blank Form - start from scratch.

Migrating from Typeform? Do not use Import from URL. Use the Typeform integration under Settings → Integrations → Migrations. With API access granted it pulls the entire form - every question, all the conditional logic and all historic responses.

Question settings

Add questions with the + button. Every question has the same set of controls.

Title and description

The title is the question itself. It is a rich text field: colour individual words, underline them, bold or unbold them, and mix styles within one question. The description is optional supporting text underneath - use it for context such as "please include your postcode".

Versions and timing

An advanced but powerful block:

Versions (A/B) - create a second version of the question and split test it. Traffic is divided between them.
Time of day - show a version only during set hours and on set days. A common pattern is version A between 09:00 and 17:00 asking "would you like to be called now?", and version B out of hours offering only a booked time.
Only show at certain times - the simpler form of the same idea. Outside the window the question is skipped entirely, with no second version needed.

You can add more than one time range per version.

Question type

Short text, long text, email, phone, number, single choice, multiple choice, dropdown, date, rating, scale, statement, consent and privacy policy, calculated, and hidden field.

Always use the email and phone types for email and phone - not short text. Typed fields map automatically to the contact record and unlock partial capture, verification and booking auto-fill.

Branching

Add rules directly on the question: if this field is answer A go to question three, if it is answer B go to question four, all other cases go somewhere else. This is the recommended place to build logic - the Logic tab is for reviewing it.

Required

Recommended for most questions. If a question is not required a respondent can skip it, and if you are paying for the traffic you usually want the answer. Required questions also stop disqualified leads slipping through.

Compliance tick box

Switch this on to show a consent checkbox under the question - typically on the first question. You set the wording, which words become a link (for example "Privacy Policy") and the URL they open.

Grid layout, icons and scoring

Choice questions can render as a grid of large buttons - two, three or four per row - with an icon on each. Big buttons are far easier to tap on a phone and easier to read for anyone without perfect eyesight, and in our testing bigger buttons and text lift conversion rate. Keep them within reason: a question with many options has to use a smaller size to stay on screen.

Each option can also carry a score, so you can lead-score across the whole form (worst answer 1, best answer 3, and so on).

Save contact at this point

Creates the contact as soon as this question is reached. It only works if an email or phone has been collected before this point.

Capture partial response here

Saves this answer and everything before it, so a lead who abandons the form is not lost. You can add a tag on partial capture. That tag behaves like any other: it starts automations, and will start a live transfer if you have a rule on it. Remember: creating a contact part-way through a form will fire any automation triggered by "new contact" or "new lead", so check your automations before turning it on.

Value / reference

On the right of each question is an auto-generated reference you can copy into an automation to insert that question's answer into a message.

Meta tracking

Once you have set up a Conversions API preset (name, pixel ID and access token, tested in settings), a question can fire a Meta event when it is reached - and a calendar question can fire a separate event when a time is actually booked. No pixel needs to be installed on top of the form, which saves paying someone to wire up the Conversions API for every new form. Most people only fire events on the ending, but per-question events let you track "reached the booking step" as well as "booked".

If a form is set to report a conversion but no preset is assigned to that form, or the client has no usable connection, the form editor shows an amber warning with a link to Settings → Conversions API so you can fix it before submissions are skipped.

Bookings inside a form

You can place a booking question anywhere, but if you do:

Always route the respondent to an ending after the booking, and put your redirect on that ending.

The ending is what saves the response. If a booking question redirects straight out of the form, you get the booking but lose the form data. The alternative is to enable partial capture before the booking question, but routing through a redirect ending is the cleaner pattern.

Endings

Endings are the screens at the finish of the form, and they carry most of the routing decisions.

Type and content - pick an ending type and fully customise the heading and body text. Most forms have at least a qualified ending and a disqualified ending.
Pipeline routing - map the ending to a pipeline and stage. A disqualified ending should normally have none.
Add respondent as contact & pipeline lead - on by default. Turn it OFF on disqualifying endings, otherwise someone you have just told you cannot help is added to your contacts and pulled into your automations.
Tracking - fire a Meta event when this ending is reached. You would not normally send a disqualification back to Meta as a conversion, since it teaches the algorithm to find more of those people.
Calendar - use the built-in booking calendar or paste a Calendly URL or embed code. Because the ending saves the response first, a redirect after booking is safe here.
Versions and timing - endings support the same A/B and time-of-day rules as questions.
Redirect - the respondent never sees the ending; they are sent straight to your URL.

Responses are still recorded for disqualified respondents, so you can review them later even when no contact is created.

Logic

The Logic tab draws every branching rule as a tree, so you can see the whole journey at a glance and confirm that each path reaches an ending. You can add rules here, but building them on the question itself is usually quicker.

If a path does not reach an ending, Myra tells you before you publish - that path would otherwise lose its response.

Design

Full visual control: theme presets, background colours and gradients, text colours, border radius, button colours and text colours, borders, and font sizing. Your logo comes through from branding automatically, and you can override it per form - useful on white-label accounts where your logo sits on one side and the client's on the other.

Two things worth spending time on:

Mobile. Large buttons and larger text are dramatically easier to use on a phone and are the single biggest design lever on conversion rate.
Accessibility. Not everyone viewing your form has perfect eyesight. Bigger, higher-contrast text makes the form usable for more people, which usually shows up as more completions.

You can also attach a custom booking calendar here, overriding the availability set in Settings for this form only.

Responses

Every submission - complete or partial - lands in the Responses tab. Questions that were skipped by logic are shown as not answered, so you can see exactly which path the respondent took. Filter by state or by Meta event, and export what you need.

Analytics

The Analytics tab shows drop-off per question, variant performance and endings reached. When you are sending paid traffic to a form this is where you find the question that is bottlenecking your lead volume - and decide whether it earns its place.

Settings

Public slug - the form's URL. Usually leave it alone.
Time zone and phone country.
Fallback confirmation message - used only when a submission does not reach an ending with its own message.
Progress bar and back navigation - back navigation is usually best off.
Fallback pipeline routing - where submissions land when no ending sets a pipeline, including partials added later.
Conversions API presets - your Meta pixel and access token.
Tags added on submit - form-wide tags. Per-ending tags are usually better.
Email and phone verification - Myra checks in a second or two whether an address or number is real. You can set a limit; past it, verification is skipped rather than blocking the respondent.
Booking auto-fill - map name, email and phone from earlier questions so nobody is asked for them twice at the booking step.
Custom booking calendar - override calendar availability for this form.

Build with AI / Edit with AI - describe the form or the change and let Myra build it.
Preview and Open public link.
Embed codes for landing pages and funnels.
History - every saved version, restorable, with the published version marked.

Forms - reference for every field and setting
Live transfers - bridge new form leads straight to a rep
Meta lead forms - route Facebook and Instagram lead ads
Booking pages - calendars and availability

If you get stuck, Support inside the app answers most form questions immediately, and you can escalate to a human at any point.