A company mailbox as a source, or as the place where a person sends a draft.
Integrations
A connection to the tools you already use.
An assistant is useful when it sits next to mail, CRM, Odoo, a helpdesk or the phone system, not in a separate tab nobody opens. Each link states what is read and who may ask.
Odoo
Odoo work in the group is done by Polskie Odoo.
Telephony
PBX and VoIP are a separate practice of World Support Service.
Systems that come up most often
- Mail: reading named mailboxes or folders, and draft replies that a person sends. The group is a Microsoft partner, so Microsoft mail environments are familiar. We do not claim to replace a Microsoft product.
- CRM: customer records and contact history, in the scope the process owner sets.
- Odoo: documents, tickets and descriptions you already keep in the system. Odoo implementations in the group are done by the Polskie Odoo team.
- Helpdesk: the solution base and ticket text as material for answers from sources.
- Telephony: a transcript or a note after a call only where the organisation has a basis to record at all. PBX and VoIP are handled by World Support Service.
How we describe a connection
Each integration keeps a short note: which fields reach the model, whether they stay in the index, who has an account, and how to switch it off. Without that, “integration” is only a heading.
We do not keep a plugin catalogue that promises every connector works. If a system has an API or an export, it can be designed. If it does not, we say so at the start.
Data in motion
A connector does not move the model’s boundary. Content it fetches is computed locally. We do not add it to a cloud language API.
Connector logs can keep more than they should. Cutting what remains in the journal is part of the work described under compliance.