How the AI desk works.

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.

A sponsor email, from arrival to next step

  1. It arrives.

    The sponsor writes to the business address. The message lands on the desk with everything else the business received today.

  2. AI proposes the areas.

    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.

  3. It names an owner and a next step.

    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.

  4. The owner taps Confirm or Fix.

    One Confirm creates the records in every area at once. If something is wrong, Fix corrects it first, and any area can be unticked.

  5. The correction teaches the desk.

    Each Fix teaches the sorting this business's habits. That learning stays with the business and is not used to train a shared model.

One item, seen from several areas.

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.

  • Interactions
  • Leads
  • Research
  • Operate
  • Schedule
  • Finance
  • Presence
  • Obligations
  • Team
  • Development

Every source enters the same sorting flow.

Every source feeds the same sorting. Here is where each connection stands.

Working today

Email. Works end to end today, on test data while the product is in development.

Built, in testing

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.

Designed

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.

A person approves what goes out.

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.