How do you do order entry for orders that arrive by email?
Order entry for an order that arrives by email or as a PDF happens by hand today; Bombos reads the order and the attachment, finds the customer and gets a schedule proposal with a draft confirmation ready for you to process.
Works with your own scheduling software, calendar and accounting package.
The order email is the first task, then your office team processes more work, and better work, with the same people.
This is how it goes now, and how it goes with Bombos.
Regular customers order by email with an attachment, or with "just the same as last time", and the office staff look everything up and retype it.
Today, someone on the office team reads the email, finds the customer and retypes the job into your software. "Same as last time" sits above the attachment. First, they must identify the customer, the job address and what is being requested. A request through Jobber's client hub is already processed digitally, but with a separate email, the work starts with reading and looking things up.
The order from the email and the attachment is ready for your schedule, with the confirmation to the customer attached.
The job is ready as a proposal, with the details your schedule needs. Bombos reads the email and PDF and finds the customer details. You see the requested work, customer and address, with the reason they belong to this job. The draft confirmation is ready beside it. You review the proposal, correct anything that is wrong and send the confirmation. After your approval, the job enters your schedule.
After three months, every order is in your schedule without anyone retyping it. Your office team reviews instead of entering data, even with a PDF or "same as last time." The same people process more orders. Because your team knows how Bombos learns, they set up the next task themselves.
What's ready for you then
- Every order email is ready for scheduling
- Including the PDF and "same as last time"
- The customer confirmation is ready beside it
- More orders processed by the same office team
Where do you see that?
The order that came in sits on the list of proposals in Bombos, with the details found and the draft reply attached. You see which email was read and why that customer was attached to the order. You read the description from the attachment next to the customer details found and adjust the work order proposal. The draft confirmation belongs to that same job, so you read the text to the customer next to the content of the order. Your package does not have to be open beside it.
With "ready for you" you see that the preparation is waiting for your review. "Waiting on your input" means there is still a question, for example about the address where the work has to happen. That question sits with the email and the attachment you are looking at. In the log for this job you find every action with an effect outside Bombos. It shows what happened with the order, alongside the work that is still only a draft.
How does it start?
It starts with a conversation of about an hour in the first week, in which we go through an order email with an attachment together. Which inbox receives the orders, where do the customer details live and which scheduling package do you use? You say which details you need before an order can be processed. We also agree who decides when the email and the attachment say different things about the work.
After that, Bombos starts the first task at "proposing". The reading, lookup and preparation start with the order and the attachment as they come in. You keep your own package and inbox, nothing moves and no training is needed; we set it up together. If you correct a customer found or the reading of a request, that correction is the rule from then on. Without those corrections, Bombos does not learn how you read a request. More room per task type, through "run after approval" or "run on its own", you only give once the work has gone well for a while. The confirmation to the customer still needs your approval.
The order email is the first task, not the whole offer. We take you along on that first step, and after that your own office staff teach Bombos the next task. We would rather you did not keep coming back to us. After three months, every order is in your schedule without anyone retyping it.
More orders with the same office team.
Retyping an order requires no judgment, yet a person still does it. A fast-growing business gets more of these emails every month, and the office team fills up first. You do not want to grow headcount, and good people are hard to find. With Bombos, your office team does more work, and better work, with the same people.
After order emails, your team teaches Bombos the next task. They do not need technical skills. Your people approve or improve proposals every day and naturally learn to work with AI. We guide you through the first step, and we do not want you to keep coming back to us.
Leave your number and we call you back to talk through how orders reach your team today.
What Bombos does, in three steps
It reads what comes in
An email, a message, a photo or a PDF: Bombos reads it, looks up the client and the details in the systems you already have, and sees what is missing.
It drafts the work, you approve it
The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.
It remembers what you decide
Every correction becomes the rule for next time. Once a kind of task has gone well for a while, you hand it over step by step, and you check the log afterwards.
What can Bombos not do here today?
An order only becomes a final work order after you have approved it; Bombos does not make one out of every incoming email by itself today. On the list sits the proposal with the details for processing and scheduling. A description in a PDF can be unclear. If the email names a different visit address than the attachment, you decide which address is right; Bombos puts that question to you instead of guessing an address.
What a customer only mentioned by phone is not in the email or the PDF. That is why Bombos interviews you about it: it asks what was agreed verbally about the job, so that information is in the proposal right away next time. The customer found and the summary of the work can contain mistakes too, so check them.
No confirmation goes to a customer without someone at your company pressing Approve. That limit covers every channel and is technically enforced. Only Bombos can switch it off, at your explicit request and at your own risk. A delivery date that has not been agreed yet does not belong in that message as a promise. The work starts with the email; the decision is about the job you make of it.