PBJ RingCentral — Changelog

Current release: 7.13 (September 2026)

7.13 — 11 September 2026

Update PBJ CRM to 7.35 at the same time — PBJ CRM 7.35 carries a database change (27 to 28) that has not yet run on a live MySQL host. Take a database backup before you update. There is no database change in this plugin.

This release also carries 7.03 through 7.12, which were tested on our own site rather than published one at a time: the text and call inboxes matching the email inbox’s button bar, Call spelled and placed the same way on both and struck through with a reason when there is no number, Create or open ticket on both inboxes, safer Add to ticket handling for messages and calls, a known number recommended on the conversation, Add to ticket reopening a closed ticket, and Convert+ opening the CRM’s one six-target grid.

• A text conversation opens in the CRM’s new three-pane record page, and it finally shows a contact card for the person at the other end — their number, and their name and company where we know them. Until now the counterparty appeared nowhere on the record but the title. Messages stay as bubbles, because there is only one channel on the record.
• NEW: Delete conversation moves the conversation to the CRM’s restorable bin — OWNER OR ADMIN ONLY — and a binned conversation leaves every list and count.
• RENAMED: the old “Bin” verb is now “Move to Bin folder”, and it has moved into the More menu. It never deleted anything and it still does not — it moves the conversation into your RingCentral Bin folder, where it is still there and can be moved back. It was renamed so it cannot be mistaken for the new Delete, which is a different thing on a different store.
• Convert to ticket now uses the CRM’s own Convert dialog instead of this plugin’s “Create ticket?” box, so it offers the same targets as everywhere else.
• The details on the record read CHANNEL, LINE, MESSAGES, FIRST and LAST. There is no opt-in row, because nothing here stores consent.
• The inbox and the reading pane are unchanged.

7.02 — 7 September 2026

• Housekeeping: the translation template shipped with the plugin (languages/) had been left behind at an older version, so it no longer matched the text in the plugin. It has been regenerated. No code, settings or database change — the plugin behaves exactly as 7.01 did.

7.01 — 6 September 2026

• Text conversations say File, not Close — a text is moved between piles, like an email, and the record header no longer folds Add to ticket away.
• Texts and calls declare their record id, so Convert+ can address them (it answered “That record does not exist” before), and a conversation converted to a ticket lands in the Tickets pile linked to its ticket, exactly as Make ticket does. The counterparty number travels with the conversation so a ticket can be made for a first-time texter.
• Call recordings declare the call’s length to the player so the time shows before playback, and the call details row reads “Call duration” — a recording is shorter than its call because recording starts after the call connects.

7.0.0 — 4 September 2026

7.0.0 — THE SUITE MAJOR, requiring PBJ CRM 7.0.0. One equal version across the suite. No schema change — DB stays 3.

Full release notes: PBJ CRM Suite 7.0.0.

1.12.0 — 2 September 2026

Empty call and text folders now show a short line explaining what will appear there, drawn with the CRM’s shared empty-state frame so they match every other empty screen in the portal. No database change.

1.11.4 — 31 August 2026

RingCentral now honors the CRM activity cursor budget inside its own scoped reads. Its rows remain in Everything, legacy CRM callers remain supported, and the provider no longer forces an unbounded history load. No database or version-floor change.

1.11.3 — 30 August 2026

Security hardening on the convert-to-work handoff. When a conversation is turned into a ticket, invoice or visit and the screen has asked “is this for the person or for the business they work at”, the chosen business is now validated against the businesses that person actually belongs to — exactly what the code always documented but never enforced. An unrelated or nonexistent business is refused with one non-revealing error; leaving the choice off behaves byte-for-byte as before, and if the CRM relationship check is unavailable the override is refused rather than accepted unchecked.

1.11.2 — 29 August 2026

A text or call from a sender with no valid phone number and nothing attached no longer breaks its reading pane — the Who group is omitted when empty, as the Assignment group beside it already was.

1.11.1 — 29 August 2026

Number attach is declared as two controls, Business and Person, each opening the CRM picker narrowed to that kind. The CRM core draws them as chips on the record’s title line.

1.11.0 — 29 August 2026

• The setup half of the RingCentral screen opens in the CRM. The Client ID, the redirect address, the two “bring this in” switches and the wording you show your own people are all editable without leaving the portal.
• Connecting an account, disconnecting one, choosing which business lines to use and the callback device stay in the website admin, and the screen says so and why: every one of them can break a working connection or change which number a text goes out from.
• Changing the Client ID is still refused while any RingCentral account here is connected – the same rule the website admin applies, with the reason given instead of a blank refusal.
• There is still no Client Secret anywhere in PBJ. This install signs in with PKCE and never asks for one.
• “Delete everything on uninstall” is deliberately not offered here.

1.10.0 — 28 August 2026

• A conversation can be added to a visit, not only a ticket, and the row then links back to the visit the way it links back to a ticket. The search offers both, and says so.
• Attaching a conversation writes one internal note on the visit carrying the messages — one note, not one per message.
• “Make ticket” asks who the ticket is for when the person who texted works at one or more businesses. Somebody who works nowhere goes straight through.
• “Add to ticket” is a search — by number, subject or customer — rather than a list of the twenty-five most recent tickets.
• Photos in an MMS appear as photos. Attachments were arriving labelled with RingCentral’s own record word instead of their real file type.
• Who a conversation belongs to is a fact in its header, set from there. The old assignment form two thirds down the pane is gone.
• Attaching a customer records the number on their CRM contact, not only in this plugin’s own table.

1.8.0 — 24 August 2026

• Text, call and voicemail surfaces now use CRM-owned item cards, readers, record sections and saved workspaces.
• Contextual actions remain in the CRM breadcrumb footer while full conversation and call routes remain available from the reader.
• Account identity, folder state, compose, RingOut, protected recordings, attachments and transcript behavior are unchanged.

1.7.0 — 24 August 2026

• Text, call and voicemail lists now use CRM-owned cards, readers, selection and saved workspaces.
• Full conversation and call links remain in the reader while bulk actions continue in the breadcrumb footer.
• Account, folder, compose, RingOut, recording, attachment and transcript behavior is unchanged.

1.6.0 — 20 August 2026

New: making a ticket out of a text or a call now moves the conversation, exactly as email does. It leaves your inbox, leaves the attention list and leaves the header counts, and lands in a new Tickets folder listed in the rail beside Inbox, Filed, Spam and Bin.

New: while that ticket is open, later texts on the same conversation land on the ticket instead of the inbox, and the help desk is told about each one as it arrives.

New: once the ticket is closed, a new text comes back to your inbox instead. A closed ticket is never silently reopened and never quietly added to, which is how a customer’s reply used to become invisible. The old ticket is offered as a suggested follow-up, so whoever picks it up can see the history.

New: the Tickets folder is not one you can move things into or out of by hand. A conversation lands there because it belongs to a ticket, and it stays with the ticket until the ticket itself is deleted.

New: tick boxes on the Text messages and Calls & voicemail lists, with a bar for Move to Inbox, File, Spam, Bin, Make tickets and Delete. Up to 200 at a time — over that it refuses rather than quietly doing the first 200. Every row is permission-checked on its own, and anything that could not be changed comes back with the reason.

Fixed: a filed or binned text conversation stayed filed when the customer texted again, so the new message was invisible in the inbox, in the attention list and in the header counts. A new incoming text now brings the conversation back to the Inbox. Spam still stays in Spam, deliberately.

Database version 2: the text-conversation and call lists learn which ticket they belong to. It is added on first load, with a repair pass for any site that recorded the update without actually receiving it.

1.5.3 — 19 August 2026

Fixed: Make ticket refused on any conversation the business started. The ticket’s origin demanded an inbound message, so a thread holding only your own outbound text answered “No inbound RingCentral communication is available” — which reads like a broken phone system when it really meant “you spoke first”. The origin now anchors on the newest message in either direction (the customer’s newest words still win when both exist), and the refusal for a genuinely empty thread says what is actually happening.

Changed: the New text screen no longer prints the whole saved-phone-number directory under the search box the moment it opens. Like the linking search, nothing is listed until you type two letters; “+ Create a new contact” stays one press away. No database change.

1.5.2 — 19 August 2026

New: the “Linked people, businesses & staff” search finds matches as you type — no Search button. Two letters starts it, changing the record kind re-runs the same search, and a slow answer can never paint over a newer one.

Fixed: when making a ticket is refused, the message now says what is actually missing — and only tells you to link the number when the customer is what’s missing. This release pairs with PBJ Helpdesk 2.42.1, which fixes the underlying “Ticket needs: source_url” refusal itself; update both together.

1.5.1 — 19 August 2026

Fixed: one long text message could silently stop text syncing for good. A live database refuses a value longer than its column, and RingCentral hands a text’s full body back in the thread’s subject line — so a message over 190 characters made the thread refuse to store, and the sync (correctly) held its place and retried that same message forever, reporting “Could not store the RingCentral thread.” Every stored field is now fitted to its column; the full text was never at risk, because the message body itself has no length limit. The stuck message syncs in on the first run after updating — nothing was lost. And when a store ever does fail again, the sync-health panel now shows the database’s own words instead of just “could not store.”

1.5.0 — 19 August 2026

Your phone inbox now feeds the CRM’s unified Inbox properly. Everything still sitting in the Texts and Calls & voicemail inbox folders shows up in the Inbox and the notification count — not just unread texts and missed calls. File an item (or mark it spam or bin it) and it clears; unread counts still ride along on the row.

1.4.0 — 18 August 2026

Texting and calling got smoother. Choosing Text on a contact’s number opens the compose screen with them filled in; filing, binning or marking spam keeps you in the folder you were working in, with an Undo at the top of the list; every text conversation has a Call button; and both the compose search and the link-a-number panel can create a contact on the spot.

1.3.0 — 18 August 2026

Phone activity joins the CRM’s Notifications and unified Inbox. Unread texts, missed calls and new voicemail are counted in the top bar and listed in the Inbox, and texts and calls are searchable from the CRM’s global search and the phone’s Find screen. No database change.

1.2.1 — 18 August 2026

Fixes the timestamp format RingCentral rejected on the message, voicemail and call history streams (“Parameter [dateFrom] value is invalid”), which 1.2.0’s independent-stream sync made visible. History requests now send the UTC “Z” form, so backfills run.

1.2.0 — 18 August 2026

Fixes the sync failure that could leave the inbox empty. When RingCentral rejected the instant-notification webhook subscription, the whole five-minute background sync stopped, so no inbound texts, calls or voicemail ever arrived. A subscription failure is now recorded and the background sync always runs; each sync stream also fails independently, so one stuck stream can no longer silence the others. The webhook subscription retries once with a shorter verification token when RingCentral rejects the token value.

Sync problems are now visible instead of silent. Apps & Assistants gains a Background sync health panel showing each stream’s state, last success, last error, webhook status and queue depth, and the Text messages and Calls & voicemail workspaces show a plain-language warning with a Sync now button whenever a background stream is failing.

A cleaner inbox. Message and call lists now show the linked customer’s name, a formatted number, the latest message, an unread badge, call direction and duration, and short timestamps. Conversations and calls open with the customer’s name in the title and a one-click link to their profile, the reply box matches the rest of the CRM, empty folders say so plainly, and Load more only appears when there is more to load. Everything fits a phone screen without sideways scrolling.

1.1.0 — 17 August 2026

Reconciliation and connection resolution now enumerate staff through the CRM’s role-filtered lookup instead of walking every WordPress user, so the five-minute sync no longer scales with total account count on sites with many customer or portal users. Uses PBJ CRM 1.50.0’s staff lookup when present and falls back safely on an older CRM.

1.0.1 — 17 August 2026

Text messages and Calls & voicemail are now separate first-class Communication workspaces. Each uses an account/folder rail, one message or call list, and one reading pane. A connected shared account no longer shows a false Connect prompt.

New Text searches visible People and Businesses, includes primary and second phone numbers, accepts a manually entered international E.164 number, and requires an account or line choice when more than one is usable. Clicking a CRM phone offers Text message, Phone call or Cancel.

Apps & Assistants now uses named staff and group choices and includes the complete per-install Private Client-side RingCentral app checklist: generated callback, six required scopes, two optional transcription/recording scopes, save, and connect.

1.0.0 — 17 August 2026

Initial native RingCentral integration: shared and personal connections, SMS/MMS, call logs, voicemail and protected audio, native voicemail transcripts, optional RingCentral AI insights, RingOut, customer/staff number links, CRM timeline links, folders, spam, trash and immutable communication origins.

Version 1 uses a Private Client-side app for one RingCentral company. Shared-account outbound SMS is limited to numbers authorized to the authenticated extension; other staff use personal connections. The Phone workspaces are canonical beyond the bounded 10,000-row CRM rollup.