Integration
BoardFill and Latitude
Ask the funded AI vendors about Latitude and you will get a shrug. Ask us and you will get a production deployment: Colonial Fences runs its BoardFill build on Latitude today, with our engineers holding direct server access and doing the API work by hand. This page exists because we actually did it.
What we connect to
- Your Latitude environment directly. Where the packaged API ends, our engineers work at the server level to wire what the agent needs.
- Your phone lines, for around the clock voice coverage with AI disclosure to every caller.
- Your website forms, quote tools, and Meta lead forms, feeding one pipeline instead of three inboxes.
What the agent reads
- Customer and job records, so the agent speaks with your shop's memory.
- Schedule and territory structure, which powers zip routed booking to the right crew.
- Open quotes and estimates, which drive the follow up sequences.
What the agent writes
- New leads and customers with full call summaries.
- Booked site visits and jobs, routed by zip to the right estimator.
- Notes, call outcomes, and follow up history, all inside Latitude where your office already works.
Honest limits
We would rather tell you what does not work on the first call than have you find out after the invoice.
- Latitude integrations are hand built. That is the honest reason nobody else offers one, and it means your deployment gets scoped in discovery against your specific Latitude setup rather than quoted off a feature list.
- Because the work is custom, changes to your Latitude configuration after launch should loop us in. The monthly tuning cycle exists partly for exactly this.
- If your Latitude instance is hosted somewhere we cannot get appropriate access, we will tell you on the first call rather than discover it in week three.