It connects to what you already run.
A recap nobody acts on is just a nicer transcript. The point is that the work leaves the app: the follow-up gets sent, the CRM gets updated, the next visit gets booked. Knack connects to your CRM, your calendar, your email and your own systems. If it has an API, it is in scope, and we build the connection with you during onboarding.
Connect today
Connected the day you start.
Reads the day's appointments so a recording lands on the right visit, and uses real attendee names to identify who is speaking.
Syncs every recap to a folder you own as Markdown, so your meeting record lives somewhere you control.
Sends the follow-up from the rep's own address, draft-first so nothing leaves without a human seeing it.
Set up with you
Built with you during onboarding, and included with an annual Team plan. Connected before you go live.
Reads the job, the customer and the lead source. Writes the quote, objections, outcome and next step back onto the job.
Read more →CRMThe visit as a note on the deal, the structured fields as properties you can report on, the next step as a task.
Read more →Job, customer and lead source in; the visit note back out.
Same loop: the appointment in, the conversation back onto the job.
Opportunities and contacts, with the visit logged as an activity.
Deals updated with what was actually said in the room.
Notes and custom fields written back after each appointment.
Post the recap into the channel that runs the day, the moment it exists.
Same, for teams that live in Teams instead.
Quoted price and outcome, where the money already lives.
Every visit appended to the sheet your reporting genuinely runs on.
Structured visit records in the base you already built.
Turn a next step into an item on the board that runs the crew.
A webhook into whatever you built in-house, including the system everyone is afraid to touch.
Read more →Why we do it this way
Every software company promises integrations and then ships the four its largest customers asked for. Meanwhile a real field business runs a stack nobody could predict: a CRM, a scheduler, an invoicing tool, a spreadsheet that is quietly load-bearing, and often something built in-house that everyone is afraid to touch.
So we do not ask you to wait for your tool to reach the top of a roadmap. Every meeting produces a structured record, and we connect that record to where your work already happens. We are a product team inside an AI agency, which means building the connection is work we do anyway.
The practical version: tell us your stack on the call. We will tell you plainly what we can wire up and what we cannot, before you pay for anything, and it is working before you go live.
Which integrations does Knack support?
Google Calendar and Google Drive are connected the day you start. Everything else, including Housecall Pro, HubSpot, ServiceTitan, Jobber, Salesforce, Pipedrive, Zoho, Slack, Teams, QuickBooks, Sheets, Airtable and your own in-house systems, is built with you during onboarding. If it has an API, it is in scope.
Is there a setup fee for integrations?
Integration setup is included with an annual Team plan. We connect Knack to what you run as part of onboarding and it is working before you go live. Genuinely unusual work, such as an in-house system with no documented API, is quoted separately, and we tell you that on the call rather than afterwards.
How long does it take to get connected?
It is part of onboarding, not a later phase. Your connection is working before you go live, because a meeting tool that is not wired into where your work already happens is a tool your reps stop opening in three weeks.
Do you integrate with my CRM specifically?
Almost certainly. The named ones on this page are the common requests, and anything else with an API is in scope. Tell us what you run and we will tell you plainly on the call whether there is a seam, rather than after you have paid.
Does Knack replace my CRM?
No. Your CRM stays the system of record for the customer, the job and the invoice. Knack fills the one gap it cannot cover on its own, which is what was actually said in the room, and writes that back as a note plus structured fields you can report on.
Does the rep have to do anything to sync a meeting?
No, and that is deliberate. Any integration that needs a tired person to press a button after their last appointment gets used for two weeks and then abandoned. The recording attaches to the right job and the write-back happens without anyone touching it.
Where does my data actually go?
Only where you connect it, and only the fields you choose. Recaps sync to your own Google Drive; the CRM write-back goes to your CRM. Where a security review demands it, the automation layer can run inside your own infrastructure rather than ours, which matters because the content is recordings from inside customers' homes.
What happens if we switch CRM later?
We rewire it. That is the advantage of treating connections as something we build with you rather than a fixed list: changing CRM is a configuration change on our side, not a reason to leave.
Tell us what you run.
We will tell you on the call exactly what we can connect, before you pay for anything.