Internal Comms & Meetings

How to schedule meetings across timezones as Small Customer Success Teams

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Your three-person team covers accounts in Singapore, London, and Chicago. Every QBR cycle you spend a full afternoon just finding a time that doesn't land at 11pm for someone. You're copying availability from Google Calendar into a Calendly link that only reflects one meeting type, bouncing emails with APs and decision-makers who are slow to respond, and manually chasing confirmations in Intercom threads. By the time the meeting is booked, you've lost two days you needed for prep. You don't have a CS coordinator. You have HubSpot, a shared Google Calendar, and a lot of unread replies.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A public booking page synced live to your Google Calendar, with separate meeting types for kickoff calls, QBRs, and renewal check-ins — each with its own duration, buffer time, and confirmation message

An automated email workflow that fires a scheduling link to the right contact in HubSpot when a customer hits a trigger (new contract signed, 60-day mark, expansion signal) — no manual send required

A post-meeting notes pipeline that captures the call, extracts action items, and pushes a summary back into the account record so your whole team stays current without a debrief

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Scheduling Email Agent Meeting Notes

Data sources & config

Starch connects directly to Google Calendar via scheduled sync to power real-time availability for the booking page. HubSpot is connected from Starch's integration catalog — the agent queries it live to watch for deal-stage changes and pull contact details for outreach. Notion is connected via scheduled sync to archive meeting notes. Intercom is reachable from Starch's integration catalog for any in-app notification triggers you want to wire.

Prompts to copy

Build me a booking page with three meeting types: 'Kickoff Call' (45 min), 'Quarterly Business Review' (60 min), and 'Renewal Check-in' (30 min). Pull availability from my Google Calendar, block 15 minutes of buffer after every QBR, and don't allow bookings less than 24 hours in advance.

When a HubSpot contact's deal stage moves to 'Onboarding', automatically send them an email with my Kickoff Call booking link. If they haven't booked within 5 business days, send a follow-up. Draft both emails in a tone that's warm but direct — we're a small team, not a big CS org.

After every meeting booked through my scheduling page, transcribe the call, pull out action items with owners, and save a summary to the account's Notion page. Flag any open action items that haven't been resolved in the summary email you send me each Monday.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Google Calendar — Starch syncs your calendar on a schedule, so your booking page always reflects actual availability including internal blocks, personal holds, and existing customer calls.

2 Start from the Scheduling app in the Starch App Store and describe your three meeting types: Kickoff Call (45 min), QBR (60 min), Renewal Check-in (30 min), each with its own slug and confirmation copy.

3 Set availability rules by timezone — e.g., Monday through Friday, 9am–5pm in your local timezone — and let the booking page handle the display conversion for customers in Singapore or London.

4 Connect HubSpot from Starch's integration catalog. Tell Starch: 'When a contact's deal stage in HubSpot changes to Onboarding, send them my Kickoff Call booking link automatically.'

5 Use the Email Agent to draft and send that outreach. Give it the tone: 'friendly, brief, CS team of three — not a corporate CS org.' Set a 5-business-day follow-up if no booking is made.

6 For QBR season, tell Starch: 'Pull every HubSpot account with a renewal date in the next 90 days, draft a QBR scheduling email for each with my QBR booking link, and queue them for my review before sending.' Review the batch in the Email Agent's draft view and send in one pass.

7 Wire Meeting Notes into every booking type. When a call ends, Starch transcribes it, generates a summary with decisions and action items, and saves it to the corresponding Notion page for that account.

8 Set a Monday morning automation: 'Compile all open action items from meetings this past week, group them by account, and Slack me a summary.' Your whole team sees what's outstanding without a separate debrief.

9 For customers in difficult timezones (APAC), tell Starch to create a separate 'APAC-friendly' meeting type that only shows slots between 7am–9am your time — early for you, reasonable for them.

10 After a booking is confirmed, trigger an automated pre-meeting email: 'Send the customer a confirmation with the agenda, a link to their last QBR notes in Notion, and a prompt to share any topics they want to cover.' Email Agent handles the draft; Google Calendar confirmation handles the send timing.

11 Track which accounts haven't booked a QBR yet using a custom dashboard: 'Show me all HubSpot accounts with renewal dates in Q2 where no QBR meeting is on my calendar in the next 60 days.' This surfaces the gaps before they become churn risks.

12 Publish the scheduling link in your Intercom message templates so customers can self-book from within support conversations — no extra step for your team.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q2 2026 QBR Cycle — March Kickoff

Sample numbers from a real run

Meridian Logistics (Chicago, renewal May 1)	47,000
Fenwick Digital (London, renewal June 15)	28,500
Apex Platforms (Singapore, renewal April 30)	61,000

You have three QBRs to book in March, totaling $136,500 in ARR up for renewal by June. In the old workflow, this would be three separate email threads, two of which would stall for a week waiting on London and Singapore decision-makers. With Starch, you tell the Email Agent: 'Pull every HubSpot account with a renewal date between April 1 and June 30, draft a QBR invitation for each with my booking link, and flag anyone we haven't spoken to since January.' The agent queries HubSpot live, identifies these three accounts, drafts three emails in under two minutes — each referencing the account name and renewal month — and queues them for your review. You approve and send. Meridian books same-day. Fenwick responds asking for 8am GMT; your scheduling page shows that slot as available and they self-book. Apex is in Singapore, so the APAC-friendly meeting type shows them a 7:30am your time option that lands at 7:30pm their time — workable. All three calls appear on your calendar within 48 hours. After each call, Meeting Notes transcribes, extracts action items (Meridian: share updated API roadmap by March 20; Fenwick: intro call with new procurement contact; Apex: co-marketing proposal), and saves summaries to Notion. Monday morning, Starch Slacks you a summary of all three open items so nothing gets lost between calls.

Measurement

How you'll know it's working

Time-to-first-meeting for new customers (days from contract signed to kickoff call held)

QBR completion rate by renewal cohort (% of accounts with an active renewal that have a QBR on the books 30+ days before renewal date)

No-show and reschedule rate by meeting type and timezone

Open action items per account older than 7 days

Average email-to-booking conversion time (hours from scheduling link sent to slot confirmed)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Calendly (standalone)

Handles the booking page well but doesn't connect to HubSpot deal stages, can't trigger outreach automatically, and gives you no post-meeting notes pipeline — you're still doing the coordination manually.

Gainsight / ChurnZero

Purpose-built for CS lifecycle management including scheduling triggers, but starts at six figures, requires a CS-ops person to configure, and is overkill for a three-person team covering 250 accounts without a dedicated admin.

HubSpot Meetings + Sequences

Native to your CRM and usable, but meeting types are basic, timezone display is clunky, post-meeting notes don't auto-capture, and you can't wire it to Notion or Slack summaries without custom workflow steps.

Google Calendar + manual email

Free and familiar, but every booking is a thread, timezone math is manual, nothing captures action items automatically, and your Monday morning debrief prep takes 45 minutes it shouldn't.

On Starch RECOMMENDED

One platform — scheduling, email agent, meeting notes all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually handle timezone display for customers booking from Singapore or London, or do I have to manage that manually?

Starch's Scheduling app syncs your Google Calendar and displays available slots in the booker's local timezone automatically — your customer in Singapore sees SGT, your customer in London sees GMT. You set your availability rules once in your own timezone and the page does the conversion. You can also create a separate meeting type with a restricted slot window (e.g., 7am–9am your time) specifically for APAC accounts.

What happens if a customer wants to reschedule after they've booked?

The confirmation email includes a reschedule link. When they reschedule, your Google Calendar updates automatically and Starch can trigger a follow-up notification to you via Slack if you want one. No manual intervention needed unless the reschedule request comes through Intercom, in which case the Email Agent can draft the response.

Can Starch connect to HubSpot and actually read deal stages, or is it just a calendar tool?

HubSpot is available from Starch's integration catalog — the agent queries it live when your automations run. That means Starch can watch for deal-stage changes, pull contact details, and trigger the right scheduling email without you doing anything manually. It's not just a booking page; it's the whole handoff from CRM signal to confirmed meeting.

We also use Intercom for customer communication. Does Starch connect to that?

Yes — Intercom is reachable from Starch's integration catalog. You can include your booking link in Intercom message templates, and Starch can query Intercom conversations live when building outreach or tracking account health. It won't replace Intercom; it connects to it.

Is the meeting transcription and notes capture automatic, or does someone have to start it?

Once you configure Meeting Notes and wire it to your booking types, it runs automatically after each call ends — no manual start required. It transcribes the call, generates a summary with decisions and action items, and saves it to your Notion archive. The Monday Slack digest of open action items is also automated once you set it up.

We're not SOC 2 certified on our end yet. Is Starch?

Starch is not SOC 2 Type II certified today — that's worth knowing if your customers have strict vendor security requirements. If a customer asks, be honest about it. Starch also doesn't offer on-prem or self-hosted deployment, so all data processing runs in Starch's cloud environment.

We have some customers who book through our website and some who we have to reach out to proactively. Does Starch handle both?

Yes. The public booking page handles inbound self-scheduling. For outbound, you use the Email Agent to draft and send scheduling invitations with your booking link — either one at a time or in a batch pulled from HubSpot. Both flows land meetings on the same calendar and trigger the same post-meeting notes pipeline.