In short
How do you show a different Calendly link in Typeform based on an earlier answer?
Give each Calendly link its own ending, and use logic to send each answer to the ending that holds its link. Or keep one ending, save the right link name in a variable, and add that variable to the end of the redirect. Either way, set a default path, so nobody lands on the wrong calendar.
On this page
- Who is this for?
- Which question should pick the link?
- How do you give each Calendly link its own ending? (Pattern 1)
- How do you build one link from a variable? (Pattern 2)
- Which pattern should you pick?
- What if the link should depend on more than one answer?
- What are the common mistakes?
- When is this not worth doing?
- How do you know it is working?
Showing a different Calendly link based on an earlier answer means one question decides which calendar a person sees at the end. These two patterns work for any business that books calls from a Typeform form and offers more than one kind of meeting.
Who is this for?
This is for you if your form already asks something that changes the call. A design studio might give small projects a 30-minute intro call and large ones a 45-minute call with the owner. A contractor might send repairs to one person's calendar and full remodels to another's.
It also helps if you tried this and it went wrong. A common complaint is that the logic looks right, but everyone still lands on the same booking page. A common cause is mixing up two jobs that logic can do:
- Deciding which question comes next.
- Deciding which ending a person sees.
Only the second job picks the Calendly link. Both patterns on this page put that choice in one place you can check.
Which question should pick the link?
Pick one question where people choose from a list. A typed answer like "around ten grand?" is hard for a rule to match. A picked answer like "$2,500 to $10,000" matches every time.
Write the rule down before you build anything:
| If they pick | They see |
|---|---|
| Under $2,500 | A kind message, no link |
| $2,500 to $10,000 | Your 30-minute intro link |
| Over $10,000 | Your 45-minute owner call link |
These answers and call lengths are only an example. If you cannot fill in a table like this, the form cannot send people by it either.
Start with one question deciding the link, not two. One question and one table are easy to test. Add a second condition once the first one works.
How do you give each Calendly link its own ending? (Pattern 1)
An ending is the screen people see when they finish the form. This pattern gives each link its own ending.
- Make one ending for each row of your table. Name them so you can tell them apart, such as "Intro call," "Owner call," and "No call."
- On each ending, add the Calendly link for that row as a button or a redirect. A redirect opens the web address by itself when the form ends. Check Typeform's own pricing page to see whether your plan includes redirects.
- Open the logic for your budget question. Add one rule for each answer, jumping to the matching ending.
- Set where everyone else goes. Point it at the "No call" ending, never at a booking link you did not mean to offer.
Where it works well: you can see every path at a glance. Anyone on your team can read it.
Where it breaks: every new link means a new ending and a new rule. A question you add later with its own jump can send people past your budget rule, so they reach the default ending.
How do you build one link from a variable? (Pattern 2)
A variable is a saved value the form fills in as people answer. This pattern keeps one ending and changes only the end of its link.
- Make a variable, such as
meeting. Check on Typeform's help center whether a logic rule can set a text variable before you build this pattern. - In the budget question's logic, set
meetingto a different value for each answer. For example,introfor $2,500 to $10,000, andowner-callfor over $10,000. - On your one ending, set the redirect to your Calendly address with the variable at the end. It becomes
<your Calendly address>/introor<your Calendly address>/owner-call. Check on Typeform's help center that a redirect can include a variable, and copy each event's exact address from your Calendly account. - Give the variable a starting value, such as
intro. Then an empty variable never sends anyone to a page that does not exist.
Where it works well: there is one ending to keep up to date. A new meeting type is one new rule, not a new ending.
Where it breaks: the finished link is built at the end, so the only sure check is to submit the form yourself. One typo in a value sends people to a page that does not exist. If the variable is never set, the link is wrong for everyone.
Which pattern should you pick?
| Pattern 1: one ending per link | Pattern 2: one link from a variable | |
|---|---|---|
| Best for | Two or three links that rarely change | Several links, or links you add often |
| Easy to read | Yes, each path is visible | Less so, the link is built at the end |
| What breaks it | A missing jump or a wrong default ending | A typo or an empty variable |
| How you notice | Someone sees the wrong ending | Someone sees a page that does not exist |
| Different message per link | Yes, each ending has its own words | No, one message for everyone |
Pick Pattern 1 if you want different words beside each link, such as "Bring your floor plan" for remodels. Pick Pattern 2 if the words stay the same and only the calendar changes.
You may also be able to pass the person's name and email to Calendly, so they do not type them twice. Check Calendly's help center for how its links do this, and Typeform's help center for how to add answers to a link.
What if the link should depend on more than one answer?
Sometimes the right call depends on two things, such as budget and start date. Both patterns can do this, but the rules grow fast. Two questions with three answers each make nine combinations to check.
A simpler way is to decide one thing at a time:
- Use the second question only to skip the call. For example, "Not before next year" ends on a message saying you will be in touch closer to the date.
- Let only the budget question choose between your Calendly links.
If both answers really need to count, you are scoring the lead, not only routing it. Giving points for each answer and offering a call above a cut-off is often easier to keep right than a long list of jumps. The guide to lead routing rules for a small service business shows how to write those cut-offs.
In Qualiform, your own rules, run in code, decide what a lead is offered from its score out of 100. When a rule offers a time, the AI says your closing line exactly as you wrote it, with your scheduling link beside it if that is how your form books.
What are the common mistakes?
- Jumping between questions and expecting the ending to change. A jump to the next question does not pick the link. Only a jump to an ending does, or the variable.
- Leaving the default path on a booking link. Anyone no rule catches sees it. Point the default at a message, not a calendar.
- Rules that overlap. If "Over $5,000" and "Over $10,000" both match, check which rule runs first. Typeform's help center is the place to confirm which rule runs when more than one matches.
- Changing an answer's words after building the logic. If you rename "$10k+" to "Over $10,000," check that the rule still points at it.
- Testing only the answers your team would pick. Broken links often sit on the answer nobody tries.
- Changing a Calendly event and not rechecking the link. The form still works, so nothing warns you. Open each link yourself after any change in Calendly.
When is this not worth doing?
When every call is the same call. If your intro and your owner call are really one 30-minute meeting, use one link. Then nobody lands on the wrong one.
When you get only a few inquiries a week. Reading them yourself and replying with the right link takes minutes. A person can also see "small job, but a repeat client" in a way no rule can.
When the answer that decides the call is typed, not picked. A rule cannot match "depends on the quote." Turn it into a list, or offer one general call and sort it there.
When the routing should live in Calendly. If Calendly can do the routing you need on your plan, building it in two tools gives you two places to fix. Check Calendly's own site for what its routing does and which plans include it. The comparison of Qualiform and Calendly and the comparison of Qualiform and Typeform cover how each tool handles this.
How do you know it is working?
Submit the form yourself once for every answer on the list. If people can skip the question, submit it once skipped too. For each run, write down which page opened.
| Answer you picked | Page you expected | Page that opened |
|---|---|---|
| Under $2,500 | No call message | |
| $2,500 to $10,000 | Intro link | |
| Over $10,000 | Owner call link | |
| Skipped | No call message |
Every row should match. Run it again each time you change an answer's words, add a question, or rename a Calendly event. After a week of real inquiries, check that the people booked on each calendar are the ones you meant to see there. For the questions that come before this one, read the guide to qualifying leads from your contact form.
Common questions
How many Calendly links should one form send people to?
Two or three is usually enough. Each link is one more meeting type to keep up to date and one more path to test. If you would not run the calls differently, use one link.
Should every answer lead to a booking link?
No. A call is the most expensive reply you can give. Answers that are not a fit can end on a short, kind message that says what happens next, such as a reply by email within two days.