Help Centre
CRM · FREQUENTLY ASKED QUESTIONS

How do I connect a client's calendar to the Cold Email Agent?

Steps to connect a client's calendar to the Cold Email Agent.

Calendar setup is tied to the user who will take the call. In a client workspace, the client or assigned salesperson should connect their own Google or Outlook calendar and meeting link, then you route bookings to that person.

For agencies, this is why the one-workspace-per-client pattern exists: client calendar, client meeting link, client-specific AI SDR context.

Set it up

  1. Switch into the client's workspace (click workspace name in top-left).
  2. Go to SettingsEmail & Calendar.
  3. Click Connect on either Google Account (Email/Calendar) or Outlook Account (Email/Calendar).
  4. Sign in with the calendar account for the person who will take calls, or have them complete this step themselves.
  5. In Create events on, choose the calendar where meetings should be created.
  6. In Check for conflicts, toggle on calendars that should block busy slots.

Who needs to sign in

You have two options:

OptionHowWhen to use
The client signs in directlySend the client a link to Settings → Email & Calendar in their workspace, or have them log in and do it.Clients who want their real calendar controlled.
You sign in with a delegated accountAsk the client to share their calendar with a Google or Outlook account you control, then connect that account.Clients who don't want to log into the platform.

You do not need to manually paste a meeting link into campaign emails. For AI SDR bookings, the call handler should also set Settings → Conferencing to either a static meeting link or dynamic Zoom links.

If you want Google Meet, paste a static Meet link in Settings → Conferencing.

Match the handler and their setup

The AI SDR uses the campaign's Assigned Salesperson first, then the workspace Assigned Call Handler, then automatic assignment. Make sure the selected person has both calendar and conferencing setup complete before campaign replies start coming in.

On this page