The 360 customer board
The 360 board is one screen that shows where you stand with one customer. It gathers invoices, orders, deals, tickets and more, so you do not open six menus.
Who this is for: everyday users who work with customers.
You need: Edition: The board itself is in Basic. The cards come from bridge modules. Pro adds cards for invoices, sales, CRM, purchase, inventory and projects. Business adds cards for tickets, telephony and mail. See Editions.
Open it
- Open a contact or a company in Odoo.
- Click MitDesk Board in the button box at the top of the record.
MitDesk users see this button. If you open the board without a customer, you see a small start page. It links to Decisions and to the list of customers and contacts.
If a chat window is open, the board pins this customer to it. The chat then follows the board. See Chat.
The cards
Each installed bridge module adds one card. The cards you can see depend on your apps:
| Card | Module |
|---|---|
| Invoices / AR, Analytics / KPIs | minddesk_account |
| Orders / Sales | minddesk_sale |
| CRM / Deals | minddesk_crm |
| Purchase | minddesk_purchase |
| Inventory / Purchase | minddesk_stock |
| Projects | minddesk_project |
| Tickets | minddesk_helpdesk |
| Telephony / Calls | minddesk_voip |
minddesk_maildesk |
A card shows a main number, a second line and a few rows. A row has the record name, its state (for example Posted or Paid), an amount and sometimes a warning. Click a row to open the record.
The cards are read with the same checks as the chat, so the board never shows more than you may see:
- If a bridge module is not installed, its card is left out.
- If Odoo access rules refuse you, the card shows a lock and "No access to" the app.
- If a MitDesk rule of your administrator refuses the read, the card is left out. The board does not show the difference between this and a missing app.
The Needs attention strip under the header repeats the cards that a bridge marked with a warning.
The AI summary
The header has a short AI summary. It uses only the facts on the cards. The model must not invent numbers, records or states. The summary ends with one line that starts with "Next:" and names one action.
Cards you may not read are not part of the summary. The summary shows which provider wrote it and when. Click sources to see the apps and records it used. Click regenerate to write it again.
If no card is readable or no model is set up, the summary says it is not available. If the provider fails, you see an error and Try again. Try again is not shown when the cause is a setting, such as a missing key.
Ask about this customer
The box at the top ("Ask MitDesk about this board…") opens the chat with this customer pinned. Your text is put in the message box. You read it and send it yourself. The answer comes from a normal chat turn with its own checks and sources.
Buttons on a card
Cards have two kinds of buttons:
- View opens an Odoo list filtered to this customer.
- A button with a hand icon, such as Send reminder, Log activity or Confirm quote, runs an action. Its tooltip says "Runs through consent".
A consent button is not a shortcut. The screen sends only the customer and the action key. The server finds the records itself, so nobody can point the action at other records. The result is one of:
- done: the action ran with your rights and is in the audit log;
- sent for approval: it is now a request in Decisions;
- refused, with the reason.
Then the board reloads.
Related
- Chat
- Decisions
- Domain bridges
- How consent works
- Dashboards: numbers for the whole business, not one customer.
- Case: receivables follow-up