Works with the tools you already use.

• The browser phone. A phone button in the corner of the desk, the same phone as the GetLibre portal's. Calls to your extension ring there too.
• Click to call next to every phone number on a ticket, a contact or a company. Without the browser phone, GetLibre rings your own phone first and then connects you.
• Who is calling. When your extension rings, a panel shows the caller, their company and their open tickets, with New ticket from this call. If two contacts share the number, you pick; ReeveDesk never guesses.
• Calls on the record. Calls, voicemails and texts show on the contact, the company and the ticket, with GetLibre's summary of the call and the recording.
• Voicemail and texts to tickets. A voicemail (with its transcript) or a text from a client opens a ticket or joins their open one, as you choose.

Rules that never bend

All calls, texts, numbers, voicemail and recordings stay in GetLibre PBX. ReeveDesk shows them and asks GetLibre to place a call or send a text when a person presses a button. It never blocks, holds or reroutes a call, and it never touches emergency calls; the desk's own call buttons never dial 911 or other special numbers.

ReeveDesk's key to GetLibre can read and ring, but cannot hang up, transfer or change anything in your phone system. ReeveDesk refuses a key that could.

The AI assistant can read calls and voicemails to help with a ticket, but it can never place a call or send a text.

What it can do

• Read tickets and their threads, and read contacts if its key allows it.
• Add private notes, for example a summary of a long thread.
• Save a suggested reply for a person to use, edit or discard.
• Suggest tags or a priority with a reason. Nothing changes until a person presses Apply.

How the server makes sure it never sends

1. The key. An assistant key can hold at most four permissions, and no key of any kind can hold the permission to send, call or text.
2. The send step. Sending needs a team member who is signed in, in that moment. A key can never start a send.
3. The sending service. Before any message leaves, it checks again that a person on your team wrote and sent it.

Ticket text is treated as data, never as instructions, and automatic tests try every route with an assistant's key on every change.

• One application per piece of software, each with its own access key: explicit permissions, shown once, stored only in scrambled form, an expiry of up to a year, and revocable at any time.
• Open a request for a client company with the person, the subject, the message and context such as the page and version.
• Safe to retry. The Idempotency-Key header means a request sent twice opens one ticket.
• Alerts from your systems open one internal ticket per alert key. Repeats add to it, and your system closes it when the problem is over. Alerts never email a client.
• A software key only sees its own requests, and only what the client sees: never notes or suggested replies.

Example request

# Open a request from your own software
POST /api/v1/requests
Authorization: Bearer <your application key>
Idempotency-Key: 5f0c9e2a-7b1d-4c11-9a52-3e6f1b0d8c47
Content-Type: application/json

{
  "product": "other",
  "company_ref": "client-042",
  "contact": {
    "name": "Front desk",
    "email": "frontdesk@client.example"
  },
  "subject": "Card reader will not connect",
  "body_text": "The reader at the front desk shows offline.",
  "priority": "normal",
  "context": { "page": "/checkout", "version": "4.2.1" }
}