The add-on Calendar gives the whole company one shared calendar: meetings, calls and tasks with a reminder for every participant, recurring meetings, and the important dates you must never miss — birthdays, anniversaries and renewals. A customer can pick a free slot themselves through a booking link, and the meeting lands right beside their card, so you see not only when it happens, but with whom and about what.

Why you need it
Appointments usually live in places that do not talk to each other: one colleague’s personal calendar, another’s notebook, a third person’s chat. Nobody sees the real picture, two meetings end up booked for the same hour, a customer waits for an answer that no longer comes, and a work anniversary is remembered only after it has already passed.
A shared calendar fixes this with plain things: every meeting has an owner and participants, everyone gets a reminder, and the customer books themselves through a link instead of a long thread about when it suits whom. And because the meeting is anchored to the customer and their working record, it is never just an empty time slot in a grid.
What it does
- A meeting with participants and an anchor. A meeting has an owner and invited colleagues (up to fifty), an anchor to the customer and to a working record — a deal, a ticket, a project. The time is given together with a time zone, and all-day meetings are supported. That way an employee sees the meeting in their own time instead of recounting hours in their head.
- Recurring meetings. The familiar recurrence rules are supported: every day, on weekdays, every second week, once a month. The schedule is expanded as needed. One series is one record, but if a single occurrence changes, it becomes its own exception record while the rest stay in place: editing one meeting never rewrites the whole series.
- Meeting statuses. Planned, the meeting took place, the person did not come, the meeting was cancelled. The transitions between states run as separate commands, so the history shows what happened and when.
- Reminders for every participant. A meeting can carry up to five reminders, the farthest two weeks out. A reminder reaches each person exactly once, even if the check ran several times in a row. A reminder that would arrive more than a day late is not sent at all: that is no longer a reminder but noise.
- A link to the meeting. Link templates are set for your own video-call service: the product substitutes one place in the template and hands out a ready address. A link is issued once and does not change on repeated requests — replacing it takes a separate command. The product does not host the video call itself: it only hands out the link.
- Busy time from external calendars. An employee adds a sync seat for Google, CalDAV or Exchange — with no passwords or keys — and uploads a calendar file. The busy hours appear on the grid as separate read-only marks: they are never mixed in with the company’s own meetings and cannot be confused with them. Uploading the same file again changes nothing.
- Customers book themselves. A public page with your set of meetings, working windows and rules. The chosen slot is held for the customer for fifteen minutes while they confirm: all that time the place is not offered to anyone else. The confirmation passes whole or not at all — if the place was taken in the meantime, no booking appears, and no meeting “in two places” ever arises.
- The customer moves or cancels their booking. The customer reschedules or cancels a booking themselves, within the term you named, by the key from their link — no registration needed. If the term has passed, the page itself explains that the only way on is to contact you.
- Services, not only “a 30-minute meeting”. You can offer a service with duration variants and a price. The price is just data — taking payment is not part of the product. The customer picks the service on the same booking page, next to the ordinary meeting kinds.
- Rooms, employees and equipment. Every resource has its own availability windows and its own capacity. A slot is offered only when everything is free at once: the person, the room and the needed equipment. That is why “the room is taken” is learned when the time is chosen, not at the meeting-room door.
- The booking ladder. Requested → confirmed → in progress → completed, or cancelled or no-show. The no-show status is set by the meeting itself: mark the meeting, and the booking follows it. That way the booking and the meeting hold one truth, not two contradicting ones.
- Occupancy reports. How loaded a room was, the no-show share, the list of cancellations — everything is computed from the journal at the moment you look. The no-show share always names its basis: how many meetings took place at all. No separately accumulated counters living a life of their own.
- Important dates that are never forgotten. A rule is set on one date field of the card: the customer’s birthday, the work anniversary. Once an hour the product checks the occasions and creates a task for the owner — exactly one per occasion, record and year, no matter how many times the check runs. If the date falls on February 29, in a common year the occasion lands on February 28 and the rule fires instead of skipping the year.
- A congratulations draft. A draft text with the name and the number of years substituted can be attached to the task. It is a hint for a person, not a sending: the product never mails congratulations itself — the letter goes out only from an employee.
- One workplace. The Calendar section is assembled from the tabs Grid, Booking, Services and Resources, Sync and Occasions. A customer’s or a deal’s card carries an events block — one month back and one month forward by default. The section only reads: changes are made by commands to the AI agent, which can be copied from the interface.
How it relates to other add-ons
The Calendar rests on no add-on at all: it installs and works by itself. The only thing beside it is Notifications: reminders reach people through them. If Notifications is not installed, nothing breaks — reminders keep being written to the journal, they simply do not pop up in the bell.
Booking goes well with Leads: the booking link carries a place for a lead, so an enquiry from a booking can be tied straight to the lead and its source. And the meetings and occasions themselves are visible on cards in other sections — next to the customer, the deal and the ticket.
Honest limits
- External calendars work by import only. There is no two-way sync, and that is a named decision, not an unfinished corner: changes made in someone else’s calendar do not arrive in the CRM. Handing your own meetings out can be done as a subscription file, by a separate link.
- Imported busy time is read-only: it cannot be edited or deleted from the CRM. It moves by itself — with the next file from the external calendar.
- The product does not host video meetings and does not store conversation recordings: it hands out a link to your service.
- There is no online payment for a booking: the service price is data for the customer, not taking money. Money in the product lives in the Money add-on.
- Overlapping meetings are a warning, not a prohibition: two meetings at one time can be saved, and the product will say so. Only customer booking prohibits a double-book hard, and there it is built so that two bookings for one time cannot exist.
- The read window is capped: at most two months of the grid are shown at a time. A wider request refuses by name — the calendar is a working surface, not an export.
- Not every recurrence is supported: only the familiar set of rules, not the full standard of recurring events.
- A resource’s capacity is taken into account, but group sessions are not built: one slot is sold to one customer, not to a group.
- Occasions never send a congratulation themselves. A task for a person is born, a text draft is attached as a hint — and that is all; the sending stays with the employee.
- A reminder more than a day late is never sent, and a meeting link is not re-issued when its template changes: an address already handed out stays as it is.
All add-ons → Add-ons catalogue