Skip to content
LiveAgentPro Docs
Reference

What's New

A dated log of notable product changes on the current 0.x line.

LiveAgentPro is pre-launch, so this tracks the current 0.x line; once versions are cut, each release line will keep its own notes. Dates are the date the change landed in the product.

Entries below are grouped by date, newest first. Where a date could not be established from the record it is omitted rather than guessed.

2026-08-23 — Permission roles now mean something, and hosts can sign in #

  • Permission roles are enforced. Until now the roles you assigned on the Team page changed nothing: a Recruiter, a Manager and a read-only Analyst could all reach the same screens. Every screen now checks the role, so "this person may not touch payouts" is a promise the product keeps. Agency admins are unaffected — they still reach everything.
  • New permission groups for money and settings. Statements and compensation plans are separate, so someone can reconcile a month without being able to change what hosts are paid. Marking a statement paid is its own permission, and no role holds it by default except Admin.
  • Existing staff keep the access they have. Anyone who was working without a role is given a Legacy Access role that reproduces exactly what they could reach before — with the single exception of marking payouts paid. Replace it with a real role from the Team page whenever you're ready.
  • Hosts can sign in to the portal again. Signing in from the portal's own address now works; previously a host who signed out was told their password was wrong. The sign-in page now carries your agency, so send hosts the link from your portal rather than a bare address. (A host who forgets their password still needs a fresh invitation — self-service reset is not built yet.)
  • Undo actually works. The undo button on a change entry was never reachable. It is now, for agency admins, and it restores the record rather than only marking the entry undone.
  • Monthly Statements is in the menu. It was previously reachable only from inside a host's record.
  • Failed messages say so. Sending a WhatsApp message when the channel isn't connected reported success. It now tells you it failed, and the send button explains itself before you write anything.
  • Regions hold in more places. Another region's application form, message templates and audit entries are no longer visible to a region-restricted user, and agency-wide events and templates are now visible to everyone again.

2026-08-18 — Your country decides how your hosts get paid #

  • Payout details now follow your agency's country. Brazil keeps CPF, PIX key and key type exactly as they were. Colombia gets what a Colombian payout actually needs: document type (CC, CE, PPT, TI or NIT) and number, a wallet — Nequi, Daviplata, a Bre-B key or Movii — and a bank account with its type (ahorros or corriente) and number. Any country we have not modelled yet now gets an international set (tax or national ID, bank, account number) instead of a bare address box, which is what non-Brazilian agencies were left with.
  • Compensation plans can be priced in Colombian pesos. Each country offers its own currencies — reais and dollars in Brazil, pesos and dollars in Colombia — and diamonds, beans and points everywhere. Amounts are written and read in your own separators, so 50.000 typed by a Colombian is fifty thousand pesos, not fifty.
  • Statements show the currency they were actually paid in. The payment column used to be headed "Payment (BRL)" and rendered every amount as reais, whoever was reading it. It now follows the tier that matched, and your country when no tier says otherwise.
  • The country list is in your language. It was rendering in English inside a Spanish panel.
  • Changing your country never deletes payout details already on a host record; it only changes which fields the form shows. See Agency Settings.

2026-08-18 — Export everything yourself, and see what automations did #

  • The inbox is now a shared inbox. Threads can be assigned (one owner each, "Assign to me" in a click, or back to the unassigned queue), resolved and reopened, and carry internal notes that are stored apart from messages and never delivered to the host. Opening a thread no longer clears its unread badge — reading is not handling — so the count now means "messages nobody has dealt with"; Mark unread puts one back. The list filters by owner and by open/resolved. See Conversations Inbox.
  • Full self-service data export. Settings → Export your data builds a zip with one CSV per record type — 49 of them — plus a manifest naming every column that was left out. No request, no ticket, and it keeps working if your subscription lapses. Archives stay downloadable for 14 days. Admins only. This replaces "a fuller export is available on request", which is what these docs used to say. See Exporting your data.
  • The Terms of Service, the DPA and the Privacy Policy now say so too. All three were reissued as version 2026-08-18 to describe the self-service export — who can run it, what it contains, what it deliberately leaves out, how long an archive lasts, and that it works with a lapsed subscription — in place of the old "available on request" wording. The Terms and the Privacy Policy are documents you accept, so every agency is asked to accept the new versions once at sign-in.
  • Application forms are shareable at last. The form's page now leads with its public link, copyable in one click, plus Preview form and a Live / Not live badge — previously there was no way to get a specific form's link out of the panel at all. "Slug" is now Link name, with the finished URL shown as you type. Duplicate form copies a form and its questions, not live, for review. See Application Forms.
  • Write your own application questions. Alongside contact-field mapping, a question can be short text, long text, a number, a date, or a single choice from options you write. Answers are validated on the server by type and shown on the application under the wording you asked. New forms start with five standard questions in place.
  • Automations keep a run history. Inactivity rules and onboarding sequences now record every firing: when it ran, what it evaluated, and per host or per step what succeeded, was skipped, or failed — with the reason. A step that cannot send is recorded as skipped instead of vanishing. Inactivity rules also gained Preview audience (who would this hit, right now?) and Run now. See Onboarding Sequences and Points & Rewards.
  • Last active and Days idle columns, and an inactivity filter, on the Platform Details list. See Contacts.
  • Push notifications are rendered in the recipient's language.

2026-08-17 — A pass over what the panel was hiding #

A batch of fixes with a common theme: the product was doing the right thing and not telling you, or telling the wrong person.

  • The inbox says whether a message actually sent. Every outbound message carries its own state — Sending, Sent, Delivered, Read, or Not sent with the reason and a Retry button. Half-written replies are kept per conversation instead of being lost when you click away, search covers the whole message history, and the reply box refuses and explains itself when the channel isn't connected. Messages sent by an automation are no longer attributed to the host who received them. See Conversations Inbox.
  • Campaigns show the audience before they send. A live count and a preview of recipient names sit under the condition builder, on the view page, and inside the Run Now confirmation. One-time scheduling now works — editing a campaign used to quietly convert it to a daily recurring send. A template can be previewed against a chosen host, flagging unknown variables and variables that would render empty. A campaign you create starts inactive on Manual only. See Campaigns.
  • Paid statements are locked, enforced on the record rather than just the form, with an explicit Reopen for adjustment to correct one. Calculate from Plan now stages its numbers in the form for review instead of committing them. See Monthly Statements.
  • Pending invitations are visible on the Team page, with Resend and Revoke — "did my invitation go out?" has an answer on screen. See Team & Invitations.
  • Team, Agency Settings, User Roles, Sub Agencies and Compensation Plans are admin-only, on the page and on the URL, and nobody can change their own role. See Roles & Permissions.
  • Sub-agency scoping closed across several surfaces — statements, the inbox, dashboard widgets, navigation counts, event participants, and contact merging all respect a manager's scope now.
  • The host portal remembers a host's language. A Settings page holds the choice, it is saved on the record rather than the session, and notifications are sent in the recipient's language. The leaderboard gained a month picker and opens on the newest month with data, the Hall of Fame works (hosts in a sub-agency saw an empty one), Brazilian number and date formatting is correct, and live time reads 15h 24m. See Host Portal.
  • The points programme is visible to staff. Points balance and level as columns and filters on the roster, level and progress on the contact record, completion counts and a completions list per mission, Recalculate missions now, and an end date that must fall after the start date. Hosts still cannot see any of this — that half is in the unreleased mobile app. See Points & Rewards.
  • The staff panel reads dates in your language. Typing 14/03/1999 in Spanish or Portuguese now means the 14th of March, not the 3rd of December. The support section is translated, and the in-app help button opens its dialog instead of disappearing. See Getting help and Localization.
  • Public application forms accept submissions again after a regression that returned an error on submit.

2026-08-16 — Billing and support hardening #

  • Managing agency billing now requires admin rights on the account.
  • The Stripe webhook endpoint is provisioned automatically on deploy, and an unsigned webhook is never accepted.
  • Support tickets record the build they were filed against.

2026-08-13 — Support ticketing #

  • In-app support tickets. A help button on every admin page files a ticket with the page, route, diagnostics, and an optional screenshot attached; a Support page under Settings holds the full form and every ticket thread on the account. Admins only. See Getting help.

2026-08-06 — Search, naming, and translations #

  • Contacts are findable from global search.
  • Changes is now called the Audit Log — same feature, clearer name. See Audit Trail & Undo.
  • Panel navigation and dashboard widgets are translated.
  • The agency legal documents are published in Spanish and Brazilian Portuguese alongside English. The English text governs. See /policies.

2026-07-24 — Public pages translated #

  • The public marketing and registration pages are translated, and a visitor can pick a language.
  • The full set of legal documents is published and enforced: Terms of Service, Privacy Policy, Acceptable Use Policy, Data Processing Addendum, Sub-processor list, Host Terms, and Host Privacy Notice. Consent is recorded at registration and re-requested when a gated document's version changes.
  • DPA acceptance is recorded against the agency rather than an individual staff member, so there is a dated, versioned record for procurement reviews.
  • Erase one host's personal data while keeping the de-identified financial record — statements, payouts, commission and points history — so tax and accounting obligations survive the erasure. See Contacts.
  • A fuller per-agency data export, in addition to the contacts CSV that stays available even to a lapsed account.
  • Lapsed agencies are permanently deleted after the export grace period.

2026-07-06 — Setup wizard #

  • An optional first-run setup wizard walks a new agency through naming its points currency, seeding starter gamification content, and inviting its team.

2026-07-04 — Custom domains, and mobile groundwork #

  • Custom domains and white-label branding on the Agency plan: DNS verification, routing to the host portal, and automated TLS certificates. See Custom Domains.
  • Groundwork for a host mobile app — an Expo project, a token-authenticated host API, and push-notification delivery end to end. The app itself is not released, and the host-facing points, missions and rewards screens live only there; see Points & Rewards.

2026-07-03 — Points, missions, rewards, and levels #

  • A points economy: a wallet and full transaction ledger per host, with expiry, FIFO consumption, and refunds that don't inflate lifetime totals.
  • Missions — automatic, hourly-evaluated targets across nine metrics.
  • A rewards store and a redemption queue with approve, fulfil and reject (reject refunds the points and restores stock).
  • Levels earned on lifetime points, and a Hall of Fame.
  • Inactivity rules that can deduct points, and manager goals.
  • PIX and CPF payout fields for Brazilian hosts.
  • Compensation tiers can pay in points instead of cash or a service.

See Points & Rewards for what is and is not reachable by hosts today.

2026-06-18 — Billing moved to Cashier #

  • Subscription billing moved from Laravel Spark to Laravel Cashier + Stripe behind the shared Pelton Solutions billing packages. Plans and prices are defined in the app and reconciled to Stripe. See Billing.

2026-06-15 — Web conversation channel #

  • A conversation can run over the web channel, with the reply method switching back when the host answers by email.

2026-06-09 — Email in both directions #

  • Managed email sending — send through Live Agent Pro's own infrastructure with no API key, monitored for deliverability: if an agency's complaint rate climbs, non-critical mail is paused automatically while critical mail still goes out.
  • Inbound email now works. Replies to managed sends thread back into the originating conversation, with the sender matched to a contact where possible. This corrects an earlier note in these docs that said inbound email was deferred — it was, for eight days in June, and then shipped. One real limitation remains: threading only applies to managed sending. An agency using its own provider (Resend, Postmark, Mailgun, SMTP) gets no reply address from us, so its replies go to its own mailbox and never reach the inbox.
  • The inbox is unified across channels — WhatsApp and email in one place.
  • Phone numbers are validated and stored in international format, so numbers from any country work.

2026-06-01 — Conversations and this documentation #

  • Messages are organized into multi-party conversations with attributed senders and a chat-style inbox.
  • Inbound WhatsApp is ingested with media attachments and sanitized HTML.
  • Group replies are built behind a feature flag pending the Meta Groups API.
  • This public, multilingual documentation site launched (English, Spanish, Brazilian Portuguese).

2026-05-29 — Alerts, bulk actions, and reporting #

  • Tier proximity and goal achievement alerts notify hosts over WhatsApp and in the portal.
  • Bulk tagging and bulk WhatsApp from the contacts table, a contacts CSV export, event RSVP with a summary, an earnings forecast, the notification bell, a recruiter dashboard, and the profile-photo generator.

2026-05-27 — Messaging and compensation #

  • The WhatsApp messaging layer over each agency's own Meta Cloud API number.
  • Agency-configurable compensation plans with condition trees, and automatic tier assignment on each statement.