If your accounting firm uses Karbon, every client meeting has two jobs.
The obvious job is getting the meeting into the calendar. The second job is getting the right information into Karbon so the team knows what to do next. That second part is where firms often lose time.
A prospect books a discovery call, but the sales job still needs to be created. A new client books onboarding, but company details still need to be copied into the organisation record. A client answers a check-in question that points to an advisory opportunity, but the answer sits in a form response instead of becoming part of the client process.
The new Karbon integration in calendr.so is useful because
booking forms and qualifying forms can collect data at the point of booking and send mapped information into Karbon. Depending on your setup, calendr.so can create or update people and organisations, populate Karbon contact fields, create a Karbon job, assign it to the booking host, and add a timeline note with the booking details.
That gives firms a practical way to connect scheduling to the work that happens after the meeting is booked.
1. Discovery calls: create a Karbon work item for the sales process
Discovery calls are often the first place where useful data enters the firm.
The prospect gives you their name, email, company name, service interest, company registration number, current accounting setup, deadline pressure, and sometimes the reason they are looking to move firm. If that information only lands in an email notification or calendar invite, someone still has to turn it into a sales process.
With the Karbon integration, you can set up a discovery booking page so the form collects the details you want before the call. If the prospect is new, calendr.so can create the person and organisation in Karbon. The booking can also create a sales or triage job, assign it to the host, and add a timeline note with the booking details and form answers.
A simple version might look like this:
- The prospect books a discovery call from your website.
- The form asks what they need help with, company name, registration number, current software, and best contact details.
- calendr.so creates or updates the Karbon person and organisation.
- A sales or discovery job is created in Karbon and assigned to the person hosting the call.
- The booking summary is added to the Karbon timeline so the host can prepare without searching through emails.
This is useful for firms that want a more consistent sales process without building a heavy CRM setup. Karbon remains the place the team works from, while calendr.so handles the booking and intake step.
2. Onboarding: fill Karbon person and organisation fields before the call
Client onboarding is where small missing details turn into delays.
A team member joins the call and then has to ask for basic information that could have been collected when the client booked. The client's job role is missing. The company registration number is missing. The organisation record exists, but the fields the team relies on are incomplete. The onboarding call starts with admin rather than momentum.
For onboarding, the Karbon integration makes
booking forms more useful because the form can populate mapped Karbon fields directly. That means the firm can ask for information once, during the booking flow, and have it appear against the right person or organisation in Karbon.
You do not need to turn the booking page into a full onboarding questionnaire. The form should collect the handful of details that affect setup, ownership, or preparation. For example:
- Company registration number.
- Client contact role.
- Trading name or group structure details.
- Current bookkeeping or payroll software.
- The internal person who should attend the onboarding call.
If the meeting needs more than one internal person, use
multi-host booking so the client only sees times when the required people are available. For a more controlled firm-wide rollout, use
team event types so the onboarding page, form questions, location, buffers, and booking rules stay consistent across the team.
The practical win is simple: the client books the onboarding call, the meeting lands in the calendar, and the data the team needs starts appearing in Karbon before the call happens.
Check-ins are useful when they surface a reason to speak. They become noise when every client is pushed into the same meeting regardless of need.
A qualifying form can help you separate clients who need a call from clients who only need to confirm a few details. The form can ask practical questions, then route the client based on their answers.
For example, an accounting firm might ask:
- Are you planning to sell your business in the next three years?
- Are you expecting a major change in revenue, profit, or headcount this year?
- Have you bought or sold any major assets since we last spoke?
- Are you considering taking money out of the business in a different way?
- Have you had any tax, payroll, VAT, or cash-flow concerns you want to discuss?
If the answers suggest a useful conversation, the client can be directed to a booking page for a review, tax planning call, advisory discussion, or partner check-in. If the answers do not suggest a call is needed, they can be directed to a thank-you page on your website.
This is where
qualifying forms become more than a way to collect information. They help the firm decide whether a meeting should happen, and if it should, which meeting is appropriate.
With the Karbon integration, the collected information can still land in Karbon. That means the team does not lose the context if the client is routed to a thank-you page, and the host has useful notes if the client is routed to a booking page.
What to set up first
Do not try to rebuild every client meeting workflow on day one.
Pick one booking flow where the team already feels the pain. For most firms, that will be discovery, onboarding, or a specific check-in campaign. Decide which Karbon fields should be updated, whether the booking should create a job, who should own that job, and what should be included in the timeline note.
Then test it with a few real bookings before rolling it out more broadly. You want the form to collect enough information to help the team, but not so much that clients abandon the booking.
The firms that get the most from this kind of integration will not be the ones with the longest forms. They will be the ones that decide which client details should be captured at the moment of booking, and where that information needs to appear in Karbon so the next person can act on it.
Why this matters for accounting firms
After working with hundreds of accounting firms, one pattern comes up again and again: the practice management system may be well designed, but the client action often happens outside it.
The client books a call. The client fills in a form. The client gives useful context. Then the team has to copy that information into the system where the work is managed.
calendr.so's Karbon integration helps close that gap. Discovery calls can create sales work. Onboarding forms can populate client details. Check-in forms can route clients to the right next step and keep the answers attached to the client record.
The goal is not to add another form to the firm. The goal is to make the booking process feed the system your team already uses to run the work.