Here is one email followed from arrival to done, using a writer's sponsor inquiry. Email works today and AI sorting is in testing. The Confirm and learning steps are the design being built now.
The sponsor writes to the business address. The message lands on the desk with everything else the business received today.
The AI reads it and proposes the areas it belongs to: Interactions for the conversation, Leads for the new sponsor, Schedule for the proposed date and Finance for the fee.
It picks who should handle it from the people allowed to see it, and suggests what to do next, like reply to the sponsor or confirm the date.
One Confirm creates the records in every area at once. If something is wrong, Fix corrects it first, and any area can be unticked.
Each Fix teaches the sorting this business's habits. That learning stays with the business and is not used to train a shared model.
The ten areas are lenses on the same item, not copies of it. The sponsor email stays one message, and each area shows only the part it needs, with links to the rest.
Every source feeds the same sorting. Here is where each connection stands.
Email. Works end to end today, on test data while the product is in development.
Website forms. Local tests cover sending a submitted request into the desk.
Business software. The owner setup and local tests cover a connection for requests from a business's own software.
Connector foundation. The shared read-only connection foundation has local tests. Google Calendar provider testing is still ahead.
Webhooks. Named software connections are designed to send updates into the desk.
Google Calendar. Approved, read-only calendar details are designed for a later provider test.
Gmail and Outlook. Selected mailbox messages are designed to enter the same sorting flow.
Everydom prepares the work and a person decides. Anything that sends a message or changes something outside the desk waits for someone to approve it.