Internal Comms & Meetings

How to schedule meetings across timezones as Small HR Teams

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

You're coordinating interviews between a hiring manager in Austin, a candidate in London, and a panel member who works flex hours — and you're doing it over email. Your Google Calendar shows your availability but not theirs. Greenhouse tells you when the interview is scheduled but not whether the Zoom link got sent. You're the one manually checking time zones, sending three rounds of 'does Thursday work?' emails, then re-sending the calendar invite when someone's on Outlook and the original didn't land. For a two-person HR team already running onboarding, PTO reconciliation, and review cycles simultaneously, every scheduling thread you're managing manually is a 20-minute tax that compounds across 15 open reqs.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A public booking page for each interview type (15-min screen, 45-min panel, 60-min hiring manager review) that candidates and interviewers can use to self-schedule — no back-and-forth email required

Automatic meeting notes for every interview, with a summary, key impressions, and action items archived in a searchable history so nothing gets lost between rounds

An AI inbox triage layer that catches scheduling requests buried in your email, drafts the reply, and sets follow-up reminders for threads that go cold

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 Email Agent

Data sources & config

Starch connects directly to Google Calendar via scheduled sync for real-time availability; Calendly bookings also sync on a schedule if you're already using it. Gmail is connected via scheduled sync so the Email Agent reads your inbox and can send on your behalf. Meeting notes are captured from Zoom or Google Meet links on calendar events — both are reachable through Starch's integration catalog and queried live when a meeting starts. No browser automation required for this stack, though Starch can automate any web-based scheduling tool or ATS portal through your browser if your setup requires it.

Prompts to copy

Build me a booking page for our recruiting interview slots. I need three meeting types: 15-minute recruiter screen, 45-minute panel interview, and 60-minute hiring manager deep dive. Sync it with my Google Calendar, add 15 minutes of buffer between meetings, and let candidates pick their own slot from whatever's open.

After every interview, transcribe the conversation, generate a one-paragraph summary with the candidate's name and role, pull out any action items the panel committed to, and save everything to a searchable archive by candidate name and date.

Triage my inbox every morning and flag any email that contains a scheduling request, interview confirmation, or candidate follow-up. Draft a reply for each one. If I haven't responded to a candidate email in 48 hours, remind me.

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, pulling 12 months back and 3 months forward so it always knows what's actually available before showing any booking slots.

2 Open the Scheduling app from the App Store and describe your interview types: name, duration, buffer rules, and who the host is. If you have multiple interviewers with different availabilities, describe that too and Starch will build the logic.

3 Share the booking link in your Greenhouse candidate emails or embed it in your email signature. Candidates see only open slots; when they book, a calendar event is created for everyone automatically.

4 Connect Gmail via scheduled sync. Starch reads your inbox on a schedule and the Email Agent begins categorizing incoming messages — candidate replies, interview confirmations, and rescheduling requests are separated from benefits questions and payroll threads.

5 Tell the Email Agent what counts as urgent for your hiring queue: 'any email from a candidate we've moved past the screen stage should be flagged immediately.' It drafts responses you can send in one click.

6 Connect Zoom or Google Meet from Starch's integration catalog so Meeting Notes knows where to find the recording or transcript when a call ends.

7 Set up the Meeting Notes app to activate automatically for any calendar event tagged as an interview. After each call, it generates a candidate summary, extracts interviewer commitments, and archives everything by candidate name.

8 Create a lightweight custom app in Starch: 'Show me all interview rounds scheduled this week, which ones have meeting notes attached, and which candidates are still waiting for a decision email.' Describe it in plain language — Starch builds the view.

9 Set a weekly automation: 'Every Friday at 4pm, pull this week's completed interviews from Google Calendar, check which ones are missing meeting notes or a follow-up email, and Slack me a list.' Starch runs it without you touching anything.

10 For international candidates, tell Starch once: 'When generating a booking confirmation email, always include the meeting time in the candidate's local timezone as well as mine.' It applies that rule to every confirmation going forward.

11 If your ATS is Greenhouse — reachable from Starch's integration catalog — you can build a view that pulls open reqs alongside their scheduled interview slots so you see coverage gaps without toggling between systems.

12 Review and iterate: the first week, check which meeting types are getting booked and whether the Email Agent's drafts need tuning. Starch lets you update the prompt logic the same way you built it — just describe the change.

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 engineering hiring sprint — 6 open reqs, 3-week window

Sample numbers from a real run

Recruiter screen slots offered per week	20
Scheduling emails eliminated (est.)	47
Interview rounds completed across 3 weeks	34
Meeting notes auto-generated	34
Candidate follow-up reminders triggered by Email Agent	11
Hours saved vs. manual coordination (est.)	9

In April, your team is filling 6 engineering roles simultaneously with a hiring manager in Austin, two senior engineers who work hybrid hours, and candidates spread across the UK, India, and the US West Coast. Before Starch, a single panel interview required 4-6 emails to find a time, a manual Zoom link, and someone remembering to take notes. With the Scheduling app running, candidates self-book from a live availability pool — the 45-minute panel slot shows open times that work for all three interviewers because Starch is reading all three calendars. Over 3 weeks, the team ran 34 interview rounds. Every one got a meeting notes summary automatically. The Email Agent flagged 11 candidate emails that had sat unanswered longer than 48 hours and drafted the replies. The HR team estimates they recovered roughly 9 hours that would otherwise have gone to scheduling logistics — hours that went into the headcount model the CFO needed by April 30th instead.

Measurement

How you'll know it's working

Time-to-schedule: hours between candidate stage advance and confirmed interview on the books

No-show rate: percentage of booked interviews where candidate or interviewer doesn't appear (a leading indicator that confirmation emails aren't landing)

Interview note completion rate: percentage of completed rounds that have a meeting notes summary attached before debrief

Recruiter email response time to candidates: average hours between candidate message and HR reply

Open req coverage: number of open roles with at least one interview scheduled in the next 7 days

Comparison

What this replaces

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

Calendly standalone

Calendly handles booking well but doesn't connect to your inbox, can't generate meeting notes, and creates another silo — you're still manually linking what was booked to what was discussed to what needs to happen next.

Greenhouse scheduling + built-in tools

Greenhouse's native scheduling covers ATS-linked interviews but doesn't triage your inbox, doesn't auto-generate notes, and stops at the boundary of its own product — anything outside Greenhouse is still manual.

Google Calendar + Otter.ai + Gmail (manual stack)

Each tool is competent in isolation; the cost is you're the integration layer — copying action items from Otter into your tracker, chasing Otter summaries when the recording didn't process, and still spending time on scheduling emails that a booking link would have eliminated.

Notion + Zapier for HR coordination

Zapier can glue specific triggers together but requires you to design and maintain every workflow in a drag-and-drop editor — when your process changes (new interview stage, new timezone rule), you're rebuilding zaps, not just describing the change.

On Starch RECOMMENDED

One platform — scheduling, meeting notes, email agent 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

We use Greenhouse as our ATS. Does Starch connect to it?

Yes — Greenhouse is reachable from Starch's integration catalog, which covers 3,000+ apps. The agent queries it live when your app needs data. You can build a view that pulls open reqs, current stage, and scheduled interviews in one place. It won't replace Greenhouse's native scheduling UI, but it connects the data to everything else you're running in Starch.

Our hiring manager uses Outlook, not Gmail. Does the Email Agent still work?

Yes. Starch syncs Outlook on a schedule — messages, events, calendars, and contacts — the same way it handles Gmail. The Email Agent works across both. If your team is split between Gmail and Outlook, both can be connected.

What happens if a candidate needs to reschedule? Does Starch handle that?

The Scheduling app lets candidates reschedule from the same booking link — they pick a new slot and the calendar event updates automatically. The Email Agent can also catch a reschedule request that comes in via email, draft a reply with the booking link, and flag it for you to send. You're not doing the manual back-and-forth; you're approving a draft.

We sometimes interview people on platforms where the meeting isn't in our Google Calendar — like a third-party video tool. Can Meeting Notes still capture those?

If the meeting is on a platform that doesn't sync to your calendar, the direct path is to log the meeting manually or connect that platform from Starch's integration catalog. Zoom and Google Meet are both reachable. For platforms without a formal API, Starch can automate the browser session — no API needed — to retrieve recordings or transcripts if they're web-accessible.

Is Starch SOC 2 Type II certified? We handle candidate personal data.

Not yet — Starch is not currently SOC 2 Type II certified. That's worth knowing before you route sensitive candidate data through any new system. It's on the roadmap, but we'd rather you factor that honestly into your evaluation than find out later.

We have employees across the US, UK, and India. Does the booking page handle timezone display automatically?

Yes. The Scheduling app reads the booker's local timezone and displays available slots in their time. When the event is created, both sides see it in their own timezone. You can also tell Starch — in plain language when you set it up — to include the timezone explicitly in confirmation emails, which we'd recommend for international candidates who sometimes have calendar apps that don't convert cleanly.

We already have a Calendly account. Do we need to switch?

Not necessarily. Starch syncs Calendly on a schedule, so if you keep using Calendly for booking, your Calendly event data flows into Starch and you can build workflows on top of it — like the Friday recap automation that checks which interviews happened and which are missing notes. You can also migrate to Starch's native Scheduling app if you want everything in one place. Either path works.