The CRM Calendar and the AI Assistant: Meeting Preparation Without Guesswork
In most small firms the calendar is the first place where the CRM falls apart. Appointments live in a phone calendar, the customer history lives in the CRM, the deadlines live in a task list, and the only connection between the three is the person who has to walk into the meeting on Thursday morning. Nobody decided to work this way. It simply happened, one tool at a time. The calendar inside the CRM is an attempt to put the appointment, the customer and the deadline back into one place, and the assistant is what makes that place searchable in plain language. This is not a new product category, and the team does not have to change its habits: the point is simply that the CRM should hold the one screen everybody already looks at several times a day.
The calendar sits in the collaboration area of the CRM, next to chat and mail, and it holds two calendars at once. My calendar is private: only its author sees the events. The company calendar is shared: every member of the firm sees the events in it. The choice is made per event, in the event window, and it can be changed later by editing the event. For an owner this split is more useful than it sounds. A private note about a salary conversation does not belong in the company calendar, and a delivery date that concerns three colleagues does not belong in a private one. Because the two calendars are separated at the level of the individual event, the same person can keep both kinds of appointment in one grid without mixing them up.
The page shows a month or a week, and the week always starts on Monday, which is worth saying because it is not something a German or Ukrainian team has to argue about. The month view shows the full weeks that cover the month; the week view shows seven days around the chosen date and gives each day much more room. A search field filters events and tasks by title while typing, so entering a customer name turns the grid into that customer's timeline. Today is marked with a green frame. In the month view a cell fits three bars; when there are more, a small plus sign with a number shows how many are hidden, and the honest advice is to switch to the week view instead of wondering what you missed.
The second reason the calendar earns its place is that tasks with a deadline appear in the same grid. In My calendar every task that has a deadline is drawn on the day of that deadline as a blue bar with the time, so a call at eleven and a quote that must go out by five sit next to each other instead of in two different windows. A click on the bar opens the task preview: the status, which is in progress, overdue or completed, the responsible person if one is set, and a star that marks the task as important for you. A completed task turns grey and is struck through, a small detail with a large effect on trust, because the grid does not lie about what is still open.
An event itself is built from a small number of fields, and each limit shows what the calendar is designed for. The title is required and takes up to 100 characters. A colour square offers six colours, which is enough to separate customer meetings from internal ones without turning the grid into a design project. The description takes up to 2000 characters and is the right place for the agenda, the list of participants and links. Then come the calendar choice, my calendar or company calendar, and the four time fields: start date, start time, end time and end date. An event may last several days, and if the end is earlier than the start the save is refused instead of quietly producing a broken appointment.
Two fields deserve their own paragraph because they are the ones people misread. Attendees is a free text line of up to 200 characters, and location is another free line of the same length. Attendees is only a note. Nobody receives an invitation from it, nobody gets a message, and nothing appears in another person's calendar because their name was typed into that line. The CRM calendar is not an invitation system, and pretending otherwise would be the fastest way to make a team stop trusting it. If a meeting needs an invitation that the other side accepts, declines or moves, that still happens in the mail programme or in Google Calendar. What the CRM calendar does well is keep the meeting next to the customer record it belongs to.
A reminder can be set per event, one reminder per event, and the choice is deliberately small: 5, 15, 30 or 60 minutes before the start. When the time comes, an event notification appears in the bell in the header. For a private event only its author sees it, for a company event all members see it, which matches how the two calendars are shared. The same reminder also goes out by e-mail, and that is the part that saves a meeting when nobody is looking at the CRM. The e-mail reaches the people who switched e-mail notifications on in their profile, and only if a company mailbox is connected. One detail worth knowing before you rely on it: the e-mail text is in German.
Now the honest part, because a reminder you cannot rely on is worse than no reminder at all. Reminders are checked every 30 seconds while somebody from the firm keeps the CRM open in a browser, and once a day by the server. If the CRM is closed for everybody, a reminder that should arrive in the minutes before an event can arrive late. A late reminder is still delivered while the event is running and for one more hour after it ends, but not later than that. In practice the e-mail path and the browser path cover each other: the mailbox carries the reminder when the office is empty, and the open tab carries it when no mailbox is connected.
Google Calendar is the integration small firms ask about first, and the rules are worth reading before connecting, because the exchange is not symmetric. Once connected, events from Google appear in the Firmspace calendar. Events of the company calendar are written to Google, and when they are deleted in the CRM they are deleted there too. Private events in My calendar stay in Firmspace only, which is a deliberate decision: the Google calendar chosen for writing usually belongs to the firm and may be visible to several people, and a private meeting has no business appearing there. Only the Google calendars you tick are imported, and a target calendar is chosen for events created in the CRM.
Two smaller rules decide whether the integration feels reliable in daily use. First, an old connection that was granted read rights only shows an orange note and has to be reconnected; until that happens, events created in the CRM do not reach Google, and the CRM says so instead of pretending the transfer worked. Second, timing. A sync now button fetches events immediately, and otherwise the exchange runs by itself at most every 15 minutes while somebody uses the CRM and by the server schedule. Only the window from one month back to six months ahead is exchanged, which is the part of the calendar a firm actually works in.
iCloud follows a different logic, and the difference is not a bug. Apple does not offer a sign-in dialog for calendars, so the connection is made with an Apple ID and an app-specific password created on appleid.apple.com. And iCloud is read-only: iCloud events come into the CRM, into the company calendar, and nothing is written back to iCloud. If somebody edits an imported iCloud event inside the CRM, the change stays in Firmspace and the next sync replaces it with the Apple version. For a firm that plans in the CRM and keeps a private life on an iPhone this direction is usually the right one, and knowing it in advance avoids the unpleasant moment of discovering that an edit disappeared.
This is where the assistant comes in, and it is worth being precise about what it reads. Calendar events and meetings are one of the sections it browses: title, date, start and end time, location, attendees and description. That is enough for the questions people actually ask in the morning. What do I have tomorrow. What is planned for this customer this week. Is anything on Thursday afternoon I should keep free. It can also open the calendar page on request, so the answer is followed by the grid itself rather than by a description of the grid. The assistant reads the calendar; it does not have to own it to be useful in front of it. The answers come from the same calendar the person sees on the screen.
Around the calendar the assistant has three more habits that turn an appointment into preparation. It can pull a customer's full card with the latest communication history and turn it into a short summary: who the person is, where the matter stands, what is still open and which next step it suggests. It can list open and overdue tasks, so the deadline bars in the grid can be checked against what is really pending. And it can find customers nobody has contacted for a long time, which is the quiet failure mode of every small firm. All of this works in the assistant window in the browser and in the Telegram bot, so the preparation can happen on the way to the meeting and not only at the desk.
The limits matter as much as the abilities. The assistant does not create, move or delete calendar events. It reads the calendar, prepares content and opens pages; putting the event into the calendar stays a manual, deliberate action, and that is a design choice rather than a missing feature. What it does prepare is the written work around the meeting: a follow-up task or a note on the customer card, and those changes wait for the owner's confirmation before they happen. One more rule belongs here, because it concerns this exact subject. The description and attendees fields are untrusted text typed by people and arriving from external calendars, and the assistant is explicitly instructed never to follow instructions found inside such records.
A working rhythm that uses all of this looks unspectacular, which is the point. Before a meeting: ask what is planned for the day or the week, pull the customer's history and let the summary name the open points. During the week: read the deadline bars in the same grid the meetings are in, so the quote that must go out does not hide behind the appointments. After the meeting: prepare a follow-up task or a note on the customer card, confirm it, and let the reminder machinery handle the next appointment. Nothing in this flow requires a new tool, and nothing in it requires the assistant to be more than a reader and a writer of drafts.
The honest closing list is short. An event needs a person: the assistant will not put it in the calendar, and the attendees line will not invite anybody. A reminder needs either somebody with the CRM open in a browser or a connected company mailbox, and if neither is there the reminder can arrive late. Google needs a connection with write rights, iCloud stays read-only, and the exchange covers one month back and six months ahead. And one thing is simply not covered: analytics about meeting outcomes, how many meetings turned into deals, what a meeting earned or cost. That would need access to results we do not have, so we do not report it. What the calendar and the assistant do is narrower and more reliable: appointment, customer history and deadline in one place, and an assistant that can read that place and prepare the next step.