Sign in
You are currently signed out, please sign in for access to Broa.
You are currently signed out, please sign in for access to Broa.
Every message Broa took in for this company, newest first.
Loading…
| Received | Imported | Channel | Path | From | Subject | Runs | State | Age |
|---|
How your mail is moving, stage by stage. Last checked
—.
Green: every part of that card is running normally. Amber: something is running but says it cannot take work. Red: something that should be running is not answering. Grey: there is no status to show, usually because nothing can check that part from here. Grey never means a thing is down, and never means it is working.
Each card shows the worst state of its parts and then lists them. Hover a line for the detail behind it.
The figures are not a status. They are read from your own messages, and where a figure cannot be had it shows — with the reason, never 0.
Last checked —
Green, working: the part answers its health check and says it is ready. Amber, not ready: it answers, but says it cannot take work. Red, not answering: it should be running and does not answer.
Blue, not ours: someone else's system, such as a company's own mailbox. The box shows its counts; Broa does not check it on a timer, which would mean using the company's sign-in just to colour a box.
Grey, no status: nothing on this page can check that part. It may not be built yet, or it runs where the browser cannot reach it. Grey never means down, and never means working. Hover a box for which applies.
Brings saved emails (.eml files) into the company's mail, checked
like any other message. It is for old correspondence: an archive, a company's forwarded
mail. For a message that has just arrived, use Compose.
Asked first: Broa never replies to imported mail, whichever you pick.
There is no choice for live mail, on purpose. An imported message can never be answered, so a customer's old question never gets an email weeks later. The service refuses live mail here too.
| File | Outcome | Subject | Why |
|---|
Puts a message into the company's mail as if it had arrived by email. Nothing after this can tell it apart, and it is trusted no more than any other message.
Into the company you are working in.
Submitting…
How big a message this company's intake takes. A company may set a limit below Broa's ceiling, never above it, and never zero: stopping intake is pausing the company, not a limit. Each limit is a setting, so a change is kept in its history and can be undone.
Loading…
| Limit | In force | Set by |
|---|
| Recorded | State | Outcome | Kind of question | Message | Way of answering | Spent |
|---|
What the assistant can read for this company: whether its indexes are current, the products and documents it holds down to the passages it reads, and what a question would retrieve. Read-only.
The quantity discounts Broa may state in a reply. Every price in a reply is worked out from these rules and the catalog list price; an email asking for more is held for a company administrator to decide. Nothing takes effect until it is saved.
Prices one product with the rules as they are in the editor now, saved or not, using the same calculator replies use. Nothing is saved or sent.
Customers who asked for more discount than the company's discounts give. Broa quoted what the discounts allow and holds the reply until an owner grants or declines; a grant changes that one reply, never the discounts. Owners decide these on the Front Office too (Company, Discounts). Every decision is recorded.
Who this company corresponds with: customers and prospects, and the people acting for them. An index only: orders, invoices and prices stay in the company's own system, reached through each party's reference.
Loading…
| Name | Kind | Relationship | Reference | Since |
|---|
A party added here is confirmed: you said who it is, so it is not asked about again.
Who works in each company and what each person may do. Open a company to see its people. There is no list of everyone to search: a person is added by their exact id at the sign-in provider, so nobody can learn which addresses exist in other companies. Making a company is on New company; pausing or removing one is on Companies.
Which mail is your own. Broa records a message from one of these senders on its thread and never drafts a reply to it, so it does not answer your own staff. A website enquiry relayed from one of your form addresses is the opposite: it is still answered, addressed to the customer the form names. Nothing here is guessed; only what you list counts. Nothing takes effect until it is saved.
The domains your company mails from. A domain also covers its subdomains,
so example.com covers mail.example.com; there is no wildcard
to write. Matched against the sender the mailbox recorded, never against a reply-to
address or a signature. Adding one is an ordinary change; removing one lets Broa draft
replies to that mail again and is recorded as sensitive.
Single mailboxes that are yours although their domain is not. The outside address a salesperson still uses, a contractor on their own domain. Whole addresses only. Removing one is a sensitive change for the same reason.
The addresses your website’s enquiry forms send from. Mail from these is not treated as your own: Broa reads the customer out of the form and replies to them. A relay must be one of your declared senders first: its domain listed above, or the whole address listed as yours. Where a form names nobody, the message is held for a person to look at rather than answered. Removing one is a sensitive change.
Read only: settings are changed on Settings › Settings. There one setting is saved at a time, with a preview first, and everything else stays in force.
Every row says whether it is in effect. A saved change is not in effect until it is published, and nothing here is ever changed in place.
Loading…
Each setting's value and where it came from. Name a division or a kind of question to see what applies there.
| Setting | Value | Came from |
|---|
| Name | Setting | Applies to |
|---|
| State | Comment | By | Saved |
|---|
| Version | State | Comment | By | Published |
|---|
Replaced sets are hidden here, never deleted. A rollback makes a new set, and an old set is what says which configuration produced a past reply.
Every company, where it is in Get started, and what is stuck, so one that stopped halfway is noticed before it gives up. Press the ? beside a company’s state for its details, its spend ceiling, and pausing, resuming or removing it. Its name opens the Company workspace, which asks for borrowed access first.
What people at each company asked Broa for help with. Reply, and set where it stands; the company sees each reply as from Broa.
How long Broa takes with a message, from the mailbox to a reply: each part of the way, and each step inside the pipeline, with its model and cost. Read only.
Every setting in one place, changed one at a time. Each change shows what it does before you save it, is recorded with its reason, and can be restored from its history.
How much Broa may write, read, spend and take for one email, by default for every company. Every change is recorded with its reason.
The providers Broa uses, the models it may use from each, and which model does each part of the work.
The UPS connection Broa uses to estimate Ground shipping for every company that turns it on.
Every time Broa staff open a company: who, why, for how long, and whether they could change anything. Each one was emailed to every platform administrator and is visible to the company. Mark each one reviewed once you have looked at it.
Changes that weaken a control, such as removing one of our senders or trusting a mail filter. Each one was emailed to every platform administrator. Mark each one reviewed once you have looked at it.
Switches set when this machine is deployed, such as whether replies may leave it. No screen changes them, this one included: a change is a deploy.
Tell companies about planned work, a known problem or news. Choose who sees it and when it expires; edit or withdraw it while it shows. Every change is recorded.
Mailboxes used to send approved replies, and whether Broa is reading them. Open a company's Details for its switches.
Loading…
Each company's ERP: whether Broa can read it, when it last did, the last thing that went wrong, and the request limits in force ("(own)" where the company chose its own). A company connects or replaces its key, and changes its limits, on Company settings → Connections; with borrowed access you can help there.
How much each client is using Broa, per ISO week (Monday to Sunday, UTC). Counts only: no message, no customer, no person’s name — people are counted per role. Seeing what is behind a number means borrowing access to that client, which is recorded and visible to them.
Loading usage…
Which parts of Broa each client opened this week. A screen opened is a screen opened — not time spent, and not work done. None of these figures is a billing input: the billing unit is Approved, in the table above. People are counted per role and never named.
| Client | Screens openedopens, not time | Different screenshow broadly | Busiest screensopens per screen | Actions takenof the seven | Different actions | Which actionstimes each | Per rolecounts, never a person |
|---|
Oldest week on the left. * the figure can still change (the week is open, recently closed, or a figure is not measured); ≥ some usage is known to be missing; not reported means the usage service does not send that figure at all, which is not the same as zero.
This is a screen and not an alert: nothing here is emailed and nothing is alerted on. It says who and never why — a holiday, a closed showroom and a client who gave up are the same number here — so the only move offered is the one every client offers: asking for borrowed access, with a justification the client can see.
What one company has used this period. Broa's own provider cost and margin are not shown here and are never sent to this page.
Loading…
Every decision and action Broa records, reads included. Reading this page is itself recorded. The company comes from your sign-in (or the borrowed access), never from the address. It shows the last 30 days, and each record is removed when its keeping period ends.
Loading…