Many business processes start with a message. An enquiry arrives, a customer reply, an internal question, a form, an attachment or a quick chat discussion. If communication stays outside the working data, the team later has to search for what actually happened.
That is why Apexloop connects communication to records, databases and automations.
Form as an entry into the database
Forms can be internal, public or anonymous. Their main role is to create new rows in databases. This is useful for enquiries, requests, registrations, feedback, incidents or internal requests.
A good form doesn't just save the message text. It should immediately fill in the source, segment, consent, attachments, responsible person or status. Further values can be added by formulas and automations.
Email as a record
The email page in Apexloop supports email CRUD without threads. Messages can be mapped to databases and worked with as additional records. Attachments are saved to files attachment columns and the body can be stored as backend-sanitised HTML.
Followed email is an important principle: if a message is followed, automation can work with it the same way as with other data. It can create a task, fill in a contact, send a reply or trigger an approval.
Document editor for sending
An email can be written in the document editor. The backend converts the content to email-safe HTML, so the team can use richer content without manually assembling templates.
Combined with a document page link column, this creates a practical model for newsletters: the database holds the edition, date, segment and status, while the content lives as a document page. Automation then converts the content to HTML and sends it at the right time.
Chat belongs in context
A standalone chat page is useful for direct communication within the workspace. But equally important is the chat sidebar on a document page and record. Discussion about a project, invoice or specification then stays where the decision is used.
When someone opens the record later, they don't just see the final values. They also see the relevant conversation, attachments and next steps.
Automation closes the loop
Communication becomes a process when it triggers an action. An incoming email can create a record, a form can assign an owner, a button can send a follow-up and a scheduled flow can remind of unresolved responses.
The team then doesn't need to monitor communication manually. Apexloop keeps it in data that can be filtered, calculated, printed and automated.