Everyone on the team connects their own Google Calendar and meetings travel in both directions, with a Meet link on the ones created here. On top of that you get a public booking page where somebody picks a slot that is genuinely free, and that meeting lands on the record of the company it belongs to.
What travels, and which way
Synced is a word used for a lot of different things, and nearly all of them are the same thing: a copy that updates when it feels like it. Both directions means something else, and it means exactly this.
| What you do | Where it shows up | With what detail |
|---|---|---|
| You create a meeting here | In your Google Calendar | With its Meet link |
| You create an event in Google | In your GoFeed agenda | With its attendees |
| You change the time in either one | In the other | The new time, with no duplicate event |
| You cancel in either one | In the other | Cancelled, not deleted |
| Somebody books through your public link | In both at once | With the contact already created |
The last row is the one that changes your week. A booking page that does not read your real calendar offers slots that do not exist, and the first time somebody books over a dentist appointment is the last time anybody uses that link. Here availability is your working hours minus whatever your Google Calendar already holds, with no exceptions.
Each person connects their own account and chooses which calendars come in. Nobody sees anybody else's calendar, and connecting yours publishes it nowhere: what the rest of the team sees is the CRM meetings, not your private appointments.
Connecting happens through signing in with Google, with the calendar permission asked for separately rather than buried inside a generic grant that gets accepted unread. Somebody who already connected their Google for files and would rather not lend their diary can stay where they are, and the status tells those two states apart instead of treating them as one.
Inside the booking link
A booking link is easy to picture and hard to do well, because all the work is in the details that stop it filling up with rubbish. These are the ones you control.
- Meeting types. A 30 minute discovery call and a 45 minute monthly review are two different links with two different durations, each with its own description.
- Buffers before and after. The air you need between one meeting and the next, so that three in a row do not become three in a row for real.
- Minimum notice. How far ahead the nearest slot can be booked. It is the difference between a diary and an ambush at nine in the morning.
- How far out it goes. How many days ahead can be booked, so you are not committing a Wednesday four months from now.
- Daily cap. The most meetings of that type you accept in a single day.
None of those settings is decoration. Buffers and minimum notice are what separate a diary you can keep from one that forces you to cancel, and the daily cap is the only sensible defence against a week where somebody shares your link in a group chat. The calendar does the rest: whatever is already busy is never offered, wherever it came from.
Whoever comes to book sees it all in their own timezone, with a visible selector, and the confirmation repeats the time in theirs and in yours, which is where half of all international meetings get lost. That email also carries the Meet link, a file to add it to their calendar, and two more links: change the time or cancel it. Nobody has to write to you to move a meeting.
Every meeting lands on a record
A meeting that only exists in a calendar is a meeting that gets forgotten. As it is created, attendees are recognised by their email address, the contact is found or created, and the meeting lands on the company timeline next to the calls, the notes and the open deals.
That is what lets next week's call start knowing what was said in the last one, without opening three tabs. And when somebody cancels, the meeting does not vanish: it stays marked as cancelled, with its date, because the fact that it existed is information too. A company that has cancelled twice in a row is telling you something.
An attendee is identified by their email rather than by an existing record, which is the difference between a system that works on day one and one that demands everybody be entered before they can be invited. It can be a contact you already have, somebody from your team, or a third party you only know an address for: all three are the same row, and the day that address gets a record, the meeting attaches itself to the right company.
Meetings created by hand count the same. A lunch with a former client, written down in thirty seconds with its company and its deal, is worth exactly as much in that record's history as a booking that came through the link. What matters is that nothing that happens with a company lives only in the head of whoever was in the room.
All of this is the calendar half of the commercial module, and the other half, the deals, the stages and the day's call queue, is covered in the CRM for agencies.
Everything in this article happens in one place in GoFeed.
Try it freeWhat is left out, and why
Google and nothing else. There is no Outlook connection and no iCloud connection, and the video call is Meet: there is no Zoom. Saying so early saves a 14 day trial for somebody who lives in Microsoft, and promising otherwise to win a signup would be a bad deal for both of us.
The reason is boring and honest. Every calendar provider has its own model of recurring events, of guests and of cancellations, and doing one properly costs more than doing three of them halfway. We would rather the one that is here be complete, because a sync that is right most of the time is worse than no sync at all: it gets trusted, and then it is wrong on the one morning that mattered.
It is also worth knowing what this page is not. It is not a lead capture funnel with long forms: whoever books leaves a name and an email, and everything else happens in the meeting. The documents that come afterwards live in quotes and invoices.
Who it is for
Scheduling belongs to agency workspaces and shares its home with the CRM, because they are the same conversation on two screens. That sounds administrative and it is not: the person who needs a booking link is the one selling services to other businesses and spending the day in calls that have to be remembered afterwards. A creator and an in house company have a calendar, but they have nobody to book time with and no record to leave the meeting on.
Inside an agency, two different people use it. Whoever sells uses it outwards, so that a first call books itself instead of being negotiated over email. Whoever runs accounts uses it inwards, for each client's monthly review, which is the meeting most often postponed and the most expensive one to postpone.
Setting it up this afternoon
The order that works is short. Connect your Google, pick which calendars sync, and check that what you already have shows up. Create a single meeting type, the one you repeat most, with its duration and its minimum notice. Write your real working hours, the real ones and not the ones you wish you kept, and then look at the page the way a stranger sees it.
Two details you will be glad of in the first week: set the minimum notice higher than you think you need, because lowering it is easy and getting a morning back is not, and write the meeting type description as though it were the agenda for the call. Somebody who books knowing what will be discussed turns up prepared, and that meeting runs shorter and is worth more.
From there the link lives in your email signature and on the last line of every proposal. The change is not technical, it is a habit: stop proposing three times by email and let the other person choose. If you are comparing against what you use today, that is in the Calendly alternatives.
The screens, one by one, are on the scheduling page, and what is worth having ready before a first meeting with a new client is in the client onboarding checklist.