> ## Documentation Index
> Fetch the complete documentation index at: https://docs.growthxai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Meeting Booking and Call Tasks

> Share a booking link that tracks who booked, and give your team phone calls as a sequence step.

## Booking links

We don't run a calendar. You keep Calendly or Cal.com, and the platform records the booking against the right lead.

<Steps>
  <Step title="Give each sender a booking link">
    On the sender's settings, fill in **Booking link**, for example `https://calendly.com/name/intro`.
  </Step>

  <Step title="Use it in your copy">
    `{{sender.booking_link}}` or `{{booking_link}}` in any message, InMail or email. The link carries the lead's id, so we know who booked.
  </Step>

  <Step title="Connect the webhook">
    Go to **Settings → Email & booking** and copy the **Calendly** or **Cal.com** webhook URL. Paste it into that tool's webhook settings.

    The URLs contain a secret, so only the workspace Owner can see them.
  </Step>
</Steps>

### What happens on a booking

|                |                                                                       |
| -------------- | --------------------------------------------------------------------- |
| The lead       | Moves to your **Meeting** stage, if they aren't already further along |
| The enrollment | Exits — no more automated follow-ups to someone who has booked        |
| Reports        | The meeting appears in the funnel and the cost-per-meeting figure     |
| Webhook        | `meeting.booked` fires with the lead, sender, provider and start time |

If the booking can't be matched to a lead by id, we match on the invitee's email address. If neither matches, the booking is still recorded, just not attached to anyone.

### In the Inbox

When a reply is classified **interested**, the reply composer offers a one-click **Send booking link**.

<Note>
  A booking link in an email is never rewritten for click tracking. It stays short and readable, which is what makes people click it.
</Note>

## Call task step

**Call task** (Flow group) pauses the sequence and puts a phone call on someone's task list.

* **Title** and **Script** — what to say.
* The task shows the lead's phone number.
* Whoever takes the call picks an outcome: **Connected**, **Voicemail**, **No answer** or **Wrong number**.

Each outcome is a branch on the canvas, so the sequence can react. An outcome with nothing connected falls through to **any other outcome**.

The last call outcome is also available in a **Condition** step as *Last call outcome*, so you can branch on it later in the flow.

<Info>
  Phone numbers are only stored when your imported data has them. LinkedIn does not supply them.
</Info>

## Follow step

**Follow profile** (Social group) is built and has its own daily allowance, but LinkedIn's API provider does not currently expose a follow action. The step **skips quietly** and the lead carries on to the next step. It will start working without any change on your side when the provider adds it.

If following matters to your flow, use **Send invitation** — connecting also follows.

## Related articles

* [Sequence Nodes](/sequences/creating-managing-sequences/sequence-nodes)
* [Inbox Overview](/inbox-and-manual-messaging/inbox-overview)
* [The Reports Page](/reports/reports-overview)