How do you connect FieldEdge to your inbox so that a service request by email becomes a work order on the dispatch board?
You connect FieldEdge to your inbox through the AI your team already uses, with Bombos underneath as the memory of your office. That AI reads the service request, and Bombos gives it the customer, the equipment, the service agreement and the technicians with the right skills and room in FieldEdge. The proposed work order comes with its source and the message to the customer, and if your AI has a connection to FieldEdge, it puts it there after your approval. It works next to FieldEdge, not instead of it.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
What Does FieldEdge Already Do, and What Not?
FieldEdge already handles a lot by itself. From the centralized dispatch board you assign work orders with drag and drop and match jobs to technicians by skill, location and availability. Every customer record carries the full service history, equipment details and service agreements, and you can confirm payment status before scheduling new work. Two-way texting and email marketing keep you in touch with customers.
The request itself still has to reach FieldEdge. A homeowner emails that the furnace keeps short cycling and attaches a video. A builder mails an order for equipment in three new homes. A service agreement customer replies to a tune-up reminder with a question about a rattling noise. Someone in your office reads it, finds the customer, checks the agreement and decides who goes, in between phone calls.
Your AI prepares that decision, with Bombos as its memory. It reads the email and the attachment, Bombos gives it the customer, the equipment and the agreement from FieldEdge and the technicians with the right skills and room in their day, and the proposal for the visit is ready with its source, the reason and the message to the customer underneath. An agreement that lives only in your dispatcher's head, such as which technician is certified on a particular brand, the AI asks about once and Bombos remembers.
Which Tasks Run on FieldEdge?
Each task below starts with an email and ends, after your approval, as a work order or a message in FieldEdge. Service requests are the obvious first task, because a customer without heat is waiting. Builder orders come next: the AI reads the order and prepares the work orders it contains. Maintenance under a service agreement, the quote request that comes in on a Friday evening and the reminder for tomorrow's appointments all draw on the equipment and agreement details already in FieldEdge. The order is yours to pick, starting from the work that keeps your office busiest. You start with one task, in the AI your team already uses. Bombos remembers what you agree and correct along the way, so the next task goes faster, and you do not need to be technical for that. One person can also try the plugin with their own agents first.
What Changes in Your Week?
Your dispatcher starts the day with the emailed requests already turned into proposals, each checked against the equipment on record, the service agreement and the skills of your technicians. The time goes to the exceptions instead of the lookups. Agreement customers get the quick answer you promised them, and technicians leave with the right parts in mind. Bombos is the memory under the AI your team already uses, such as Claude, ChatGPT or Copilot: it gives that AI the knowledge in FieldEdge and the way your office works, and every proposal shows where it came from.
You start with one task, and we set it up together with you, with your own FieldEdge and your own inbox. Every time you adjust a proposal, Bombos applies that choice to the next one. When the first task runs, your own team sets up the next, and from then on you do it yourself: with every correction Bombos remembers a rule, so the next task starts from what you already agreed.
What Doesn't Go Out Without Your Approval?
You approve before a work order is created in FieldEdge, a technician is assigned on the dispatch board or a text or email goes to a customer. A request from a service agreement customer can wait for that approval as well. Where that limit sits, you set per kind of work in the AI or agent itself. With the first task, we go through it together with you.
Every proposal shows where it came from: which email, which record in the package and which agreement. For the work inside your office, such as looking things up, checking and preparing, you decide how much your AI does ahead of time; messages to customers and payments wait for your approval by default. A proposal can be wrong, even when the reason sounds believable. When in doubt, your AI asks instead of guessing, and Bombos remembers your answer for next time.
Bombos also works with Jobber, Housecall Pro, and ServiceTitan.
All tasks Bombos takes on are listed under use cases.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
