Apex Desk
In progress
Every system you own eventually needs somewhere for a person to write to, and that somewhere should be yours.
See it
Cloud infrastructure engineered for the systems above. There is no public website to open; it is delivered inside a commission.
Functional scope
Inbound mail on your own domain, threaded into conversations with an owner, a status, and a history.
Routing rules, so a message about billing and a message about a bug do not land in the same undifferentiated pile.
Saved replies and a short knowledge base, so the answer someone wrote once is the answer that goes out again.
A record that survives the person who answered it, which is what makes support a system rather than an inbox.
Users and roles
Whoever answers your mail today, and whoever answers it after them.
Workflow in practice
Mail arrives, gets routed, gets answered, and stays findable.
In production
- A support address becomes a tracked conversation
- Routing puts the right message in front of the right person
- The answer written once is reused
Build status
In the shop now, with a date we will name.
Included in every system we build
This is foundation, not a product. It ships inside the systems it belongs to, and its cost is already in their figures.
If a system you are commissioning does not already carry this piece, adding it is a line in your quote, not a second purchase.
It is here so you can see what you are getting rather than take our word for it.
Rails used
Stack
- Next.js
- Postgres with row level security
- Inbound mail parsing
- Apex Relay
Handover includes
- Source for the desk surfaces
- Your inbound domain configuration
- Routing rules and saved replies
- Conversation schema and policies
Ask about Apex Desk
Tell us how your business runs today and we will show you which systems carry this piece and what they would cost you.