Cobl connects to Cal.com so every booking, attendee and booking answer feeds the deal it started: follow-up, proposal, sales deck.
Cal.com is an open-source scheduling platform. Teams use it to publish booking pages, route meetings across a team with round-robin and collective event types, and ask invitees questions before a meeting is confirmed. It runs in the cloud or self-hosted, and developer-heavy companies often choose it for that control.
Each booking in Cal.com carries more than a time slot: who booked, which event type, which team member took it, and the answers the invitee gave. That context is useful for exactly one meeting. After the call, the follow-up and the proposal are written somewhere else, and the booking that started the deal is forgotten.
Cobl reads bookings, event types, attendees and booking responses from Cal.com. That context sits inside a deal workspace next to the follow-up, the proposal and the deck, so the documents begin from the reason the buyer booked and the people who joined.
Across a longer sales cycle, bookings mark the rhythm of the deal. A discovery call, a technical session and a pricing call booked weeks apart form a sequence the documents can build on. The sequence of bookings also shows how quickly the deal is moving.
A developer tools company routes inbound demo requests through a Cal.com round-robin event. A prospect books and answers two questions: their stack and the integration they need most. The solutions engineer who picks up the booking opens a deal workspace in Cobl with it attached. The call confirms the integration question, and the follow-up drafted after it leads on that integration.
Three weeks later the prospect books a collective event with the solutions engineer and the account executive, this time with their security lead added. That booking joins the same deal, and the security questionnaire that follows starts from the same context. Nothing is sent without review.
Cobl reads bookings and the responses invitees gave in the booking form. What the buyer said they needed before the first call informs the follow-up and the proposal. The answers are often more candid than anything said later, because the buyer wrote them before any sales conversation started.
Who booked, who was added and which team member hosted each meeting sit on the deal. The workspace sees the buying group and your own team as they actually met. New attendees appearing on later bookings show the buying group growing, and the proposal can address them.
Meetings routed to different people on your team still land on the same deal. The person writing the proposal sees every meeting, including the ones someone else hosted. Handovers between team members stop losing context, because every booking lands on the same deal.
Cal.com context combines with transcripts from Google Meet, records in Attio and internal discussion in Slack. The booking explains why the buyer came, the transcript explains what they said, and the CRM holds the deal. Together they give the follow-up both the reason and the detail.
Yes. Cobl connects to Cal.com so bookings, attendees and booking responses can inform follow-ups, proposals and decks for the deal they belong to.
Bookings, event types, attendees and booking responses, read through the access the connected account holds. Bookings you do not connect to a deal are not part of its context.
The integration connects through the Cal.com API. A self-hosted instance needs to be reachable through that API for Cobl to read it, and your team controls what the connection can access.
Yes. Bookings routed to different hosts all attach to the same deal, so the documents reflect every meeting regardless of who took it.
Yes. Cobl produces a draft. Precise changes go through the inline editor and approval stays with you. More on data handling sits on the security page.