Integrations
Seven things, each said with its limits. Everything works with all of them switched off, and a switch that is off is enforced on the server, not merely hidden on the screen.
Each member of staff signs in to their own Microsoft account, and the product reads their mailbox, their calendar and their Teams chats — so an email about a block can be filed against the block, and a meeting can be saved to a building's timeline.
Their own account, not a shared one. Nothing is read on anyone's behalf, and a colleague who has not connected sees the screens say so rather than showing somebody else's inbox.
The mail screen also connects a Google mailbox (Gmail or Google Workspace) or any other mailbox over IMAP and SMTP, typed in as you would into a phone's mail app. An email can be filed against a building or a ticket whichever one it is.
One mailbox at a time, and each person's own. Outlook categories and shared mailboxes are Microsoft 365 only, and the screen says what a Google or IMAP mailbox does not do. An IMAP password is encrypted when it is stored and never shown back.
Staff can sign in with the account their agency already runs on, with two-factor authentication on top.
Where the agency allows it. An administrator turns each provider on for their own agency; until then the email-and-password door is the only one open.
Individual correspondence goes out through a Microsoft 365 mailbox the agency names, or a Google or IMAP mailbox it marks as the organisation's. Group email — one message merged per leaseholder — goes through Postmark or Mailgun.
Release is the decision. Nothing leaves until a person releases it. Once released, the server sends it within a minute. Until a mailbox or a provider is configured, released items stay queued and the outbox says why.
Demands, notices and letters that must go by post are handed to a UK mail house, printed with the address in the envelope window, and posted by Royal Mail. The letter's progress — printed, posted, returned — comes back onto it here.
Nothing is marked posted until the mail house says so. A person releases each run. A letter the mail house cannot take stays queued with its reason, and a retry never posts the same letter twice.
A supplier invoice that has been approved here can be sent to Xero as a draft bill, with a preview of exactly what will be created before anything leaves. A batch sends the approved invoices a person confirms from a list, and the list says which ones it will not send and why.
A person sends it, always as a draft. Nothing is pushed automatically, because this writes into a real set of books. Authorising the bill is a deliberate act a person takes in Xero, and a draft can be deleted there with no effect on the ledger.
An administrator connects the client bank account through the bank's own Open Banking consent page. Booked lines are fetched, and money received lands in the receipts inbox to be matched.
It reads, and moves no money. Pending lines are left out until they book. Consent lasts as long as the bank grants it, and the product says so fourteen days before it ends; only an administrator can renew it at the bank.
Card and direct-debit payments are not offered. Leaseholders pay by bank transfer, quoting the reference on their demand.
If you run something we have not named, tell us what it is and what you need from it. That is a better conversation than a logo wall.
Loading…
