Internal Comms & Meetings

How to schedule meetings across timezones as Small Marketing Teams

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

Your team spans three time zones — the lifecycle marketer is in Austin, the demand gen lead is in London, and the contractor writing next week's blog post is in Manila. Scheduling a 30-minute campaign review means a 45-minute email chain about 'does 3pm ET work for you' followed by a Google Calendar invite that conflicts with the London standup. Meanwhile you're chasing the same contractor on Slack about a deliverable that was due Tuesday. You lose at least two hours a week just coordinating when to talk — time you should be spending on the MQL-to-pipeline report your VP of Sales wants by Friday.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A public booking page with distinct meeting types (campaign reviews, contractor check-ins, cross-functional syncs) that respects your calendar in real time — anyone in any timezone books without asking

Automated meeting notes with action items extracted and assigned by name after every call, archived in a searchable history your whole team can pull from

A lightweight inbox layer that surfaces time-sensitive scheduling replies and contractor follow-ups so nothing sits unanswered for three days

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 Meeting Notes

Data sources & config

Scheduling syncs with Google Calendar as a scheduled-sync provider — Starch reads your live availability and writes new events when someone books. Email Triage connects to Gmail as a scheduled-sync provider for inbox reading and sending. Meeting Notes works within your existing meeting flow; Starch archives transcripts and extracted action items in its own database. Customer.io, HubSpot, and Notion are all connectable from Starch's integration catalog (the agent queries them live) if you want meeting action items cross-referenced against open campaign tasks or CRM contacts.

Prompts to copy

Build me a booking page with three meeting types: a 30-minute campaign review (available Tuesdays and Thursdays, 10am–3pm ET only), a 15-minute contractor check-in (any weekday, 9am–11am ET), and a 60-minute cross-functional sync (Wednesdays only, two slots). Add 15 minutes of buffer after every meeting. Pull my availability from Google Calendar in real time.

After every meeting, generate a summary with key decisions, open questions, and action items. Assign each action item to whoever was named in the conversation. Archive everything so I can search by project name or date.

Triage my inbox each morning. Flag anything that's a scheduling reply, a contractor deliverable update, or a meeting request. Summarize threads longer than five messages in two sentences. Draft a follow-up for any email I haven't responded to in more than 48 hours.

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

Walkthrough

Step-by-step

1 Connect Google Calendar to Starch (scheduled-sync provider). Starch reads 12 months back and 3 months ahead, so your booking page reflects real conflicts — including that recurring London standup that keeps eating Tuesday afternoons.

2 Connect Gmail to Starch (scheduled-sync provider). This powers the Email Triage app and lets Starch draft and send follow-ups on your behalf.

3 Open the Scheduling app from the Starch App Store and describe your three meeting types in plain English — duration, availability window, buffer time, and who the meeting type is for (contractors vs. internal cross-functional vs. external).

4 Share the booking link in your email signature, your Slack status when you're heads-down, and in the standing message you send new contractors at kickoff. No more 'when are you free' threads.

5 Activate Meeting Notes. Before your next campaign review or contractor check-in, paste the meeting link or let Starch join. After the call, it produces a summary, flags decisions made, and lists action items with the person's name attached.

6 Route those action items: if the action is a deliverable from your Manila contractor, Starch can draft the follow-up email and queue it for your approval. If it's an internal task, you can cross-reference against your Notion project database (connected from Starch's integration catalog) to see if it's already tracked.

7 Set up the Email Triage app to run each morning at 8am ET. Tell it to prioritize: scheduling replies, contractor deliverable confirmations, anything mentioning your upcoming event or campaign launch by name.

8 For the London-based demand gen lead, configure a second set of booking rules with different availability hours so their booking page reflects GMT working hours, not ET defaults.

9 Once a week — say, Monday morning — ask the Email Triage app to surface any contractor threads where a reply is more than 48 hours overdue. Draft the follow-ups in one batch rather than hunting through your inbox.

10 After your quarterly planning call, use Meeting Notes' searchable archive to pull every action item assigned to each person across the last 12 weeks. Paste that list into your retrospective doc or your Notion project tracker (live query from Starch's integration catalog) to check what actually got done.

11 If a client or agency partner needs to book time but uses a tool like Calendly already, Starch's integration catalog includes Calendly as a scheduled-sync provider — you can surface both booking streams in one view without manually reconciling two calendars.

12 Once the setup is stable, tell Starch: 'Every Friday at 4pm ET, check my calendar for the following week, identify any meetings without a confirmed agenda, and draft a one-line agenda prompt to send to each organizer.' That's an automation you describe in plain English — Starch builds and schedules it.

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

April 2026 Campaign Sprint — 3-Timezone Coordination

Sample numbers from a real run

Scheduling back-and-forth emails eliminated	14
Contractor check-ins missed due to timezone confusion (prior month)	3
Action items tracked from 6 sprint calls	31
Follow-up emails drafted by Email Triage	9
Hours recovered in one 4-week sprint	6

In March 2026 your team was preparing the Q2 paid campaign launch: new creative briefs going to the Manila contractor, a revised attribution model to walk through with the London demand gen lead, and a 60-minute sync with the VP of Sales in HQ. Over the prior month you'd lost 3 contractor check-ins to timezone miscommunication and sent 14 back-and-forth emails just figuring out meeting times. After setting up Starch's Scheduling app with separate booking pages for each meeting type, every external and contractor booking happened through the link — no email chains. The London demand gen lead booked her campaign review for Thursday 11am GMT (6am ET, which you'd pre-approved as available). The Manila contractor booked his weekly check-in for Friday 9am Manila time (3am ET — async-friendly; you reviewed his pre-meeting notes the same morning). Meeting Notes captured the 60-minute VP of Sales sync, pulled 12 action items, and assigned 4 to the demand gen lead, 5 to you, and 3 to the contractor. Email Triage drafted the follow-up to the contractor's 3 open items — you approved and sent in under 2 minutes. Net result: 6 hours recovered across the sprint, 0 missed contractor check-ins, and every action item from 6 calls sitting in a searchable archive instead of scattered across Slack threads.

Measurement

How you'll know it's working

Hours per week lost to scheduling coordination (target: under 30 minutes)

Contractor deliverable on-time rate (missed check-ins are the leading indicator)

Action item completion rate across sprint calls (tracked via Meeting Notes archive)

Email response latency on time-sensitive threads — scheduling replies and contractor updates

Number of cross-timezone meetings that required manual calendar negotiation vs. self-booked

Comparison

What this replaces

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

Calendly standalone

Handles booking well but gives you no inbox triage, no meeting notes, and no way to automate follow-ups — you're still hunting through Gmail for the contractor reply that fell off your radar.

Notion + manual meeting notes doc

Your team probably already does this — and you already know that whoever volunteered to take notes missed three action items and the doc is two weeks stale.

HubSpot Meetings

Great if every meeting is a sales call and lives inside HubSpot's CRM context; doesn't help with contractor check-ins, internal campaign reviews, or extracting action items post-call.

Otter.ai or Fireflies

Solid transcription, but it's another disconnected tool — action items live in Otter, your tasks live in Notion or Linear, your calendar lives in Google, and nothing talks to anything else without manual copy-paste.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, founder inbox 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 the Scheduling app actually block time based on my real Google Calendar, or does it use a static availability grid I set once and forget?

It reads your live Google Calendar — Starch syncs your calendar data on a schedule, so the booking page reflects actual conflicts in real time. If someone books your CEO for a last-minute sync on Thursday afternoon, that slot disappears from your contractor's booking options immediately.

We use both Google Calendar and Calendly already. Can Starch work alongside those instead of replacing them?

Yes. Calendly is a scheduled-sync provider in Starch — you can pull your Calendly events into Starch alongside your Google Calendar data. If you want to keep Calendly for external-facing booking and use Starch's Scheduling app for internal team coordination, that's a reasonable split. You're not forced to pick one.

Our contractor is in Manila and doesn't have access to our internal tools. How does the booking page work for them?

The booking page is public — it's a link, not a login. Your contractor opens it in their browser, sees your available slots in their local timezone (Google Calendar's timezone detection handles the conversion), picks one, and a calendar event is created for both of you. No account, no setup on their end.

What happens to meeting notes if we don't use Zoom — we do a lot of calls over Google Meet?

Meeting Notes works with your call setup. The specific integration path depends on how you share the recording or feed the transcript — ask Starch to walk you through the connection for your exact setup when you configure it.

Is Starch SOC 2 certified? We have a security review process for new tools.

Not yet — Starch is not SOC 2 Type II certified today. That's a real consideration if your company has a strict security review. Worth flagging to your IT or security contact before you connect Gmail or HubSpot.

Can Starch pull action items from Meeting Notes into our HubSpot tasks or Notion project tracker automatically?

Yes. HubSpot is a scheduled-sync provider — Starch connects directly to HubSpot. Notion is also a scheduled-sync provider. You can tell Starch: 'After every campaign review call, create a HubSpot task for each action item assigned to a sales team member and a Notion page entry for each item assigned to marketing.' Describe it, Starch builds the automation.

We use Customer.io for lifecycle email. Can Starch connect to it?

Customer.io is reachable from Starch's integration catalog — the agent queries it live when your app needs the data. You can build a view that cross-references Customer.io campaign sends against meeting action items or HubSpot deal stages. It won't replace Customer.io as your ESP; it connects to it so your reporting and coordination layer has the full picture.