Skip to content

Releases

PageCRM release notes

Live version v1.1.41

This page lists public product releases in plain language. It is meant for users who want to understand what changed, whether a feature is new, and how recent updates affect inbox, mobile, help, billing, and workflow behavior.

v1.1.412026-06-12Current release

WhatsApp gateway service recovery

PageCRM restored the QR WhatsApp gateway service used for Evolution-based WhatsApp connections.

What changed

  • Restored the local WhatsApp gateway so QR-based WhatsApp setup can respond again.
  • Updated platform admin service controls to manage the restored gateway service correctly.
  • Updated admin guidance so the service status matches the current production setup.

What this means for users

  • Organizations using QR WhatsApp can reconnect and continue WhatsApp setup from PageCRM.
  • Platform admins can check and control the gateway from the service management area with less confusion.
  • Existing organizations may need to scan QR again if their previous WhatsApp session was not available on the server.
v1.1.402026-06-09

Sharper layered homepage animation

PageCRM upgraded the homepage animation into a multi-layer feature deck that presents the platform modules more clearly.

What changed

  • Added separate visual layers for channel capture, pipeline execution, Sona AI, and commerce or ERP workflows.
  • Added sharper typography, darker contrast, animated progress indicators, and feature module tiles.
  • Made the hero visual easier to scan so visitors can understand PageCRM strengths from the first screen.

What this means for users

  • The landing page now explains PageCRM as a complete sales operating system more clearly.
  • Visitors can identify key modules such as inbox, contacts, products, documents, workflows, analytics, AI, and ERP faster.
  • The animation remains accessible with reduced-motion support.
v1.1.392026-06-09

Animated CRM flow hero

PageCRM added a richer animated homepage visual that explains how leads move from channels into inbox, AI routing, pipeline, documents, ERP sync, and reporting.

What changed

  • Added a visual flow for WhatsApp, email, Meta DMs, and NFC lead capture.
  • Showed how PageCRM unifies conversations, scores leads, assigns owners, and moves work through the sales pipeline.
  • Highlighted core platform strengths including shared inbox, documents, ERP sync, Sona AI, and analytics.

What this means for users

  • New visitors can understand the full PageCRM workflow faster from the first screen.
  • The homepage better communicates PageCRM as a complete CRM platform, not only a messaging tool.
  • The animation remains lightweight and respects reduced-motion preferences for accessibility.
v1.1.382026-06-09

Landing page visual refresh

PageCRM refreshed the public landing page with a cleaner enterprise SaaS presentation, stronger messaging, and smoother visual movement.

What changed

  • Redesigned the opening section with clearer PageCRM positioning for WhatsApp, email, Meta inbox, NFC, pipeline, quotations, and AI follow-up.
  • Added a polished product preview that shows the shared inbox, pipeline context, lead priority, and sales activity at a glance.
  • Improved the first-screen calls to action and benefit metrics so visitors can understand the product faster.

What this means for users

  • New visitors get a more professional first impression of PageCRM.
  • Sales teams can understand the platform value without reading long technical explanations first.
  • The page keeps the existing SEO-rich content, pricing, help links, and footer structure while improving the visual experience.
v1.1.372026-05-22

Top-bar language switch

PageCRM added a visible language switch in the main app header so users can change between English and Arabic faster.

What changed

  • Added a compact language button to the desktop top-right toolbar.
  • Added the same quick language control to the mobile app header.
  • Kept the detailed language card inside the account menu for users who need more context.

What this means for users

  • Users can switch language from any main application page without opening settings.
  • Arabic RTL mode is easier to discover on desktop and mobile.
  • The control stays compact so it does not take over the workspace header.
v1.1.362026-05-22

Arabic Shopify setup

PageCRM expanded Arabic support into the Shopify connection flow so organizations can start commerce setup with clearer Arabic labels.

What changed

  • Added Arabic and RTL support to the Shopify store connection form.
  • Translated store-domain guidance, connect action, opening state, and first sync scope explanation.
  • Kept Shopify names, store domains, OAuth behavior, and future sync scope technically unchanged.

What this means for users

  • Arabic admins can start Shopify onboarding with less English text.
  • Commerce setup now follows the same dashboard language switch as messaging, email, and Meta setup.
  • The connection remains organization-scoped for the SaaS model.
v1.1.352026-05-17

Arabic Meta connection setup

PageCRM expanded Arabic support into the Facebook Pages and Instagram connection flow so admins can manage Meta channels with clearer Arabic labels and diagnostics.

What changed

  • Added Arabic and RTL support to the Meta connection card, including connection status, add/reconnect action, page list, disconnect action, and re-subscribe control.
  • Added Arabic labels for Meta diagnostics, connected page counts, conversation counts, recent webhook hits, and setup guidance.
  • Translated the shared Meta inbox wrapper shown inside Connect Apps while keeping page names, account names, IDs, and message data unchanged.

What this means for users

  • Arabic admins can connect and inspect Facebook and Instagram channels with less English text.
  • Meta setup now follows the same dashboard language switch as WhatsApp, email, and commerce setup.
  • Operational diagnostics remain technically precise while improving readability for non-technical users.
v1.1.342026-05-17

Arabic PageCRM Email setup

PageCRM expanded Arabic support into the PageCRM Email setup area so admins can manage sender domains, DNS provider setup, mailboxes, and sender identity with clearer Arabic labels.

What changed

  • Added Arabic and RTL support to sender domain setup, verification status, DNS provider connection, and DNS record guidance.
  • Added Arabic and RTL support to mailbox creation, generated credential display, primary mailbox controls, password reset, and mailbox deletion actions.
  • Added Arabic and RTL support to sender identity settings and the link to full email settings and delivery logs.

What this means for users

  • Arabic admins can complete PageCRM Email onboarding with less English text.
  • Domain, DNS, and mailbox setup now follows the same language switch as the rest of Connect Apps.
  • Technical values such as domains, DNS records, mailboxes, tokens, and generated passwords remain unchanged for accuracy.
v1.1.332026-05-17

Arabic email setup forms

PageCRM expanded Arabic support into email provider setup flows so admins can connect Gmail, Brevo, and SMTP with clearer Arabic labels and actions.

What changed

  • Added Arabic and RTL support to the Gmail connection screen, including status, actions, setup guide labels, and feature highlights.
  • Added Arabic and RTL support to Brevo setup, including API key setup, sender identity, active provider status, test email, and delivery benefits.
  • Added Arabic and RTL support to SMTP setup, including server details, secure transport option, presets, sender identity, and test email.

What this means for users

  • Arabic admins can configure common email providers with less English text.
  • Email setup now follows the same dashboard language switch as Connect Apps, WhatsApp, and Google Merchant Center.
  • Technical values such as API keys, SMTP hosts, ports, and email addresses remain unchanged for accuracy.
v1.1.322026-05-17

Arabic provider setup forms

PageCRM expanded Arabic support into key provider setup forms so admins can connect WhatsApp and Google Merchant Center with clearer Arabic labels and status messages.

What changed

  • Added Arabic and RTL support to the WhatsApp connection card, including provider choice, QR setup, Meta official API setup, connection status, test message, and save actions.
  • Added Arabic and RTL support to Google Merchant Center setup, including account selection, data source selection, sync controls, auto-sync, setup requirements, and sync results.
  • Kept provider names, API names, account IDs, callback URLs, product feed values, and user-entered settings unchanged for setup accuracy.

What this means for users

  • Arabic admins can complete common integration setup tasks with less English text.
  • WhatsApp and commerce setup flows now follow the same dashboard language switch as the rest of the localized workspace.
  • Provider setup remains technically precise while improving readability for non-technical users.
v1.1.312026-05-17

Arabic Connect Apps workspace

PageCRM expanded Arabic support into the Connect Apps workspace so admins can choose integrations, review categories, and understand connection status with more Arabic labels.

What changed

  • Translated the Connect Apps and CRM Migration chooser, integration workspace header, category filters, status badges, plan-lock message, empty state, and common back navigation.
  • Kept provider names, app names, technical setup instructions, and organization connection data unchanged for accuracy.
  • Started the high-visibility Integrations Arabic rollout while leaving provider-specific setup forms ready for the next focused pass.

What this means for users

  • Arabic admins can navigate Connect Apps and understand integration status with less English text.
  • The integration chooser now clearly separates live app connections from one-time CRM migration in Arabic mode.
  • Provider-specific forms such as WhatsApp, email, ERP, commerce, and AI can now be translated module-by-module.
v1.1.302026-05-17

Arabic company settings

PageCRM expanded Arabic support into Company Settings so admins can manage workspace identity, localization, pipeline, notifications, AI policy, and team access with more Arabic labels.

What changed

  • Translated company profile, email signature, localization, pipeline, notification, Sona AI policy, team access, invite, and save-state labels.
  • Kept organization names, pipeline template names, member names, emails, countries, currencies, and user-entered values unchanged for accuracy.
  • Aligned Company Settings with the same dashboard Arabic switch used by Dashboard, Contacts, Inbox, Products, and Calendar.

What this means for users

  • Arabic admins can manage core workspace settings with less English text.
  • Team access and user master fields are easier to review in Arabic mode.
  • Connect Apps remains the next major dashboard workspace for deeper Arabic expansion.
v1.1.292026-05-16

Arabic calendar workspace

PageCRM expanded Arabic support into Calendar so teams can schedule, review, and manage meetings with more Arabic labels.

What changed

  • Translated the calendar toolbar, view switcher, event form, event popup, legend, status labels, and key scheduling actions.
  • Added Arabic-aware Calendar wording while keeping event titles, contact names, meeting links, and provider names unchanged.
  • Kept mobile-friendly agenda behavior and desktop calendar controls aligned with the dashboard language switch.

What this means for users

  • Arabic users can create events and review calendar activity with less English text.
  • Calendar now follows the same Arabic switch used by Dashboard, Contacts, Inbox, and Products.
  • Settings and Integrations remain the next major dashboard modules for Arabic expansion.
v1.1.282026-05-16

Arabic product workspace

PageCRM expanded Arabic support into the Product Master so catalog teams can browse, filter, and manage product records with more Arabic labels.

What changed

  • Translated the product list header, search, filters, view controls, table labels, product chips, visibility labels, and key actions.
  • Translated the product detail header, product actions, status badges, KPI labels, and main tab labels.
  • Kept product names, item codes, brands, prices, organization data, and AI prompts unchanged for data accuracy.

What this means for users

  • Arabic users can review products and open product records with less English text.
  • Product list and detail pages now follow the same dashboard language switch used by Dashboard, Contacts, and Inbox.
  • Calendar, Settings, and Integrations remain the next dashboard modules for Arabic expansion.
v1.1.272026-05-16

Arabic inbox workspace

PageCRM expanded Arabic support into the shared Inbox so teams can review queues, open conversations, and reply with more Arabic labels.

What changed

  • Translated the Inbox header, search, queue metrics, channel filters, pagination, empty states, and load-more controls.
  • Translated key WhatsApp, email, and Meta thread actions such as assign, resolve, reopen, reply, send, attachments, and message states.
  • Kept customer names, message content, provider names, and organization data unchanged while translating the workspace interface.

What this means for users

  • Arabic users can handle shared inbox work with less English text in daily workflows.
  • Mobile and desktop inbox views follow the same dashboard language switch.
  • Products, calendar, settings, and remaining deep workflow screens can continue with the same module-by-module approach.
v1.1.262026-05-16

Arabic contacts workspace

PageCRM expanded Arabic support into the Contacts workspace so daily contact work follows the dashboard language switch.

What changed

  • Translated contact search, filters, editor labels, saved views, bulk actions, empty states, and status chips.
  • Kept contact names, companies, saved view names, and pipeline stage names unchanged so organization data stays accurate.
  • Improved Arabic feedback messages for saving, deleting, rescoring, loading, and merging contacts.

What this means for users

  • Arabic users can manage contacts with less English text inside the workspace.
  • Teams can validate Contacts in RTL mode before the next modules are expanded.
  • Inbox, products, calendar, and settings can continue on the same translation pattern.
v1.1.252026-05-16

Arabic dashboard overview

PageCRM expanded Arabic support from the menu into the main dashboard overview content.

What changed

  • Translated dashboard overview headers, KPI cards, filters, table labels, and kanban actions.
  • Added Arabic due-date wording and Arabic date formatting in the dashboard overview.
  • Kept the same English/Arabic switch in the account menu for desktop and mobile users.

What this means for users

  • Users now see Arabic content inside the dashboard page, not only the menu.
  • The dashboard overview can be reviewed in RTL mode for real daily use.
  • Contacts, inbox, products, calendar, and settings can now follow the same module-by-module pattern.
v1.1.242026-05-16

Arabic dashboard labels

PageCRM made the Arabic dashboard switch visibly translate the main navigation and account menu labels.

What changed

  • Translated the primary dashboard navigation labels when Arabic RTL is selected.
  • Translated key account menu, mobile app, release, style, and logout labels.
  • Kept the language choice saved on the device so Arabic stays active after refresh.

What this means for users

  • Users can now see Arabic text after switching from the dashboard account menu.
  • The main shell feels Arabic-aware while deeper module translation continues.
  • Mobile and desktop navigation are easier to validate in RTL mode.
v1.1.232026-05-16

Dashboard Arabic RTL switch

PageCRM added a dashboard language switch so users can turn on Arabic right-to-left layout from the account menu.

What changed

  • Added English and Arabic RTL options inside the dashboard account menu.
  • Saved the selected dashboard language on the device so it remains active after refresh.
  • Adjusted the main app shell and mobile drawer direction when Arabic RTL is selected.

What this means for users

  • Users can preview and work with right-to-left dashboard layout without leaving the CRM.
  • Arabic support can now be expanded module by module on top of the same switch.
  • Mobile and desktop users get the same language control from the account menu.
v1.1.222026-05-16

Expanded Arabic public experience

PageCRM expanded the Arabic public experience with localized login, signup, pricing, and help entry points.

What changed

  • Added Arabic login and signup screens with right-to-left layout support.
  • Added Arabic pricing and help center entry pages for Arabic-speaking visitors.
  • Kept Arabic CTAs connected to the Arabic account creation flow.

What this means for users

  • Arabic-speaking visitors can move from discovery to signup with less language switching.
  • Teams can share Arabic pricing and help links with prospects and customers.
  • The product now has a stronger foundation for translating the logged-in CRM app next.
v1.1.212026-05-16

Arabic public pages and RTL foundation

PageCRM added the first Arabic public experience with right-to-left layout support for the landing page and support ticket flow.

What changed

  • Added an Arabic landing page at /ar with Arabic metadata and RTL layout.
  • Added an Arabic support page at /ar/support using the same secure support ticket workflow.
  • Added Arabic route entries to public SEO metadata and sitemap handling.

What this means for users

  • Arabic-speaking visitors can understand PageCRM before signing up.
  • Customers can create support tickets from an Arabic interface.
  • The product now has a safer foundation for expanding Arabic into login, inbox, and the full CRM app.
v1.1.202026-05-16

Organization user master and NFC profile controls

PageCRM added richer team member records and clearer public NFC profile visibility controls for organizations.

What changed

  • Added a user master area for team member employment, department, contact, location, manager, and emergency details.
  • Added a public NFC profile switch so a user profile can be hidden without deleting internal CRM data.
  • Added field-level visibility controls for public NFC profile details such as email, WhatsApp, company, bio, links, location, booking, brochure, and products.

What this means for users

  • Large organizations can maintain cleaner employee records inside PageCRM.
  • Small teams and single users can keep the profile simple while still controlling what visitors can see.
  • Public NFC profiles can share useful business details without exposing every internal user field.
v1.1.182026-05-15

Faster inbox opening

PageCRM improved inbox opening speed so teams can see existing conversations faster while channel sync continues in the background.

What changed

  • Changed inbox loading so saved WhatsApp, email, and Meta conversations appear first.
  • Moved email and Meta refresh work behind the initial view instead of making users wait.
  • Kept live updates active so new messages still appear after the inbox opens.

What this means for users

  • Users should see inbox content sooner after opening the page.
  • Large shared inboxes feel more responsive during daily triage.
  • Background sync still keeps email and social conversations updated after the first view loads.
v1.1.172026-05-15

Enterprise PageCRM Inbox polish

PageCRM improved the shared inbox interface for faster triage, clearer ownership, and a more polished high-volume team experience.

What changed

  • Refreshed the inbox header with PageCRM branding, live queue context, and clearer unread visibility.
  • Added compact and comfort density options so busy teams can scan more conversations without losing readability.
  • Improved conversation rows with stronger unread, owner, channel, status, and timestamp hierarchy.

What this means for users

  • Organizations handling large lead volumes can triage WhatsApp, email, and Meta messages faster.
  • Managers and agents can spot unassigned, pending, unread, and active work with less visual noise.
  • The inbox is more suitable for demonstrations, onboarding, and daily shared-team operations.
v1.1.162026-05-15

WhatsApp voice note support

PageCRM added voice note recording in the WhatsApp inbox so teams can respond with short audio messages from the CRM.

What changed

  • Added a record voice option in the WhatsApp inbox composer.
  • Added microphone recording controls with timer, stop, cancel, and preview before sending.
  • Voice notes are sent through the connected WhatsApp channel as audio messages.

What this means for users

  • Sales and support users can reply faster when a short voice response is better than typing.
  • Mobile and desktop inbox users get a more WhatsApp-like response workflow.
  • Teams can still preview the recording before sending it to the customer.
v1.1.152026-05-15

WhatsApp media preview improvements

PageCRM improved WhatsApp media handling so teams can view image and video messages more easily inside the inbox.

What changed

  • Added inline preview support for WhatsApp image and video messages.
  • Improved secure handling for encrypted WhatsApp media links received from Evolution API.
  • Updated media links so users can open WhatsApp files from the inbox without relying on raw provider URLs.

What this means for users

  • Teams can review customer screenshots, product photos, and videos faster from the conversation view.
  • Inbox users do not need to leave PageCRM just to understand what media a customer sent.
  • WhatsApp-heavy sales and support teams get a clearer shared inbox experience.
v1.1.142026-05-15

Inbox response and count improvements

PageCRM improved inbox visibility and platform support communication so teams can spot new work and respond faster.

What changed

  • Added menu badges for unread workspace inbox messages and new platform career/support items.
  • Improved platform admin WhatsApp replies from support and career inboxes using the platform WhatsApp sender.
  • Added inline WhatsApp image previews in inbox conversation views.

What this means for users

  • Teams can see new inbox, career, and support activity from the main menu.
  • Platform admins can reply to candidates and support requesters through the configured WhatsApp channel.
  • Image messages are easier to review inside the inbox without opening every file separately.
v1.1.132026-05-14

Shopify review compliance support

PageCRM added Shopify privacy webhook support and a clearer Shopify app landing experience for app review and installation.

What changed

  • Added mandatory Shopify privacy webhook support for customer data requests, customer redaction, and shop redaction.
  • Added HMAC verification for Shopify webhook requests.
  • Added a dedicated Shopify app landing screen after public Shopify authorization.

What this means for users

  • The Shopify app review checklist has the required privacy webhook endpoint available.
  • Merchants get a clearer PageCRM Shopify app experience after authorization.
v1.1.122026-05-14

Shopify install review flow

PageCRM improved the Shopify app installation path so Shopify can start the app authorization flow correctly during review.

What changed

  • Added a public Shopify install entry point for App Store installation checks.
  • Routed Shopify install requests from the PageCRM homepage into Shopify authorization.
  • Kept the signed-in organization Shopify connection flow available from Integrations.

What this means for users

  • Shopify reviewers can reach the Shopify permission screen from the submitted app URL.
  • Organizations can still connect Shopify from the PageCRM integrations area.
v1.1.112026-05-14

Support replies from the inbox

PageCRM support admins can now reply to support tickets by email or WhatsApp directly from the support inbox.

What changed

  • Added email reply action inside each support ticket.
  • Added WhatsApp reply action when the requester submitted a WhatsApp number.
  • Added a reusable support reply composer with a ready support-message template.

What this means for users

  • Platform support can respond without leaving the support inbox.
  • Support tickets can move faster from triage to customer response.
v1.1.102026-05-14

Support ticket detail previews

PageCRM improved the platform support inbox so admins can see ticket details and submitted screenshots directly inside the app.

What changed

  • Added inline preview for submitted screenshots and image attachments.
  • Added attachment file type, file size, and full-file open action.
  • Expanded ticket details with created, updated, resolved, assigned, organization, company, phone, source, and category fields.

What this means for users

  • Platform admins can review screenshots without leaving the support inbox.
  • Support tickets now expose more context in the detail panel for faster triage.
v1.1.92026-05-14

Cleaner support admin navigation

PageCRM cleaned up the platform support inbox layout so admin users see one clear navigation and one support inbox view.

What changed

  • Removed duplicated app shell rendering inside the support inbox.
  • Kept the public Support link out of the platform admin menu to avoid confusion.
  • Kept Support Inbox visible under the platform Administration menu.

What this means for users

  • Platform admins can manage support tickets without repeated menu sections.
  • The admin support inbox is clearer and easier to scan.
v1.1.82026-05-14

Validated support organization IDs

PageCRM now validates organization IDs on support tickets so entered workspace IDs must match a real PageCRM organization.

What changed

  • Added Organization ID validation on the support ticket form.
  • Blocked support ticket submission when a typed organization ID is not found.
  • Kept signed-in users tied to their trusted workspace organization automatically.

What this means for users

  • Support tickets are easier to match to the correct customer workspace.
  • Users get immediate feedback when they paste the wrong organization ID.
  • Platform support has cleaner organization context for registered users.
v1.1.72026-05-14

Support organization identification

PageCRM support tickets now capture organization ID details so platform support can identify the correct workspace faster.

What changed

  • Added an optional Organization ID field to the support ticket form.
  • Added copyable Organization ID visibility inside the logged-in account menu on desktop and mobile.
  • Added Organization ID visibility and search support inside the platform admin support inbox.

What this means for users

  • Support can identify registered organizations more reliably.
  • Users can copy their organization ID directly from PageCRM when raising a ticket.
  • Public users can still create tickets, but registered customers can provide stronger workspace context.
v1.1.62026-05-14

Support screenshots

PageCRM support tickets now include an inbuilt screenshot capture option so users can show the issue while creating a ticket.

What changed

  • Added a Capture screenshot button to the support ticket form.
  • Added screenshot preview and remove controls before submission.
  • Kept manual attachment upload available for files, screenshots, and documents.

What this means for users

  • Users can explain visual issues faster without leaving PageCRM.
  • Support tickets can include clearer evidence for layout, inbox, login, or setup issues.
  • Platform support can diagnose problems with less back-and-forth.
v1.1.52026-05-14

Central support ticket inbox

PageCRM added a dedicated support ticket flow so public visitors and signed-in users can raise issues that platform admins manage from one inbox.

What changed

  • Added a public support ticket page for customers, prospects, and workspace users.
  • Added file attachment support for screenshots, documents, and issue evidence.
  • Added a platform admin support inbox with status filters, search, internal notes, and resolution actions.
  • Added support access in the workspace navigation so signed-in users can find help faster.

What this means for users

  • Support requests now arrive in one controlled admin queue instead of being scattered across channels.
  • Platform admins can triage new, open, waiting, resolved, and closed tickets more consistently.
  • Users can submit clearer support requests with context and attachments.
v1.1.42026-05-13

Shopify store connection foundation

PageCRM added the first SaaS connection layer for Shopify so each organization can authorize its own store from the integrations area.

What changed

  • Added a Shopify app card in the Commerce integrations section.
  • Added a Connect Shopify flow where users enter their Shopify store domain and approve access in Shopify.
  • Stored Shopify access securely through the existing encrypted PageCRM integration token system.
  • Prepared read-only Shopify scopes for products, customers, orders, inventory, and locations.

What this means for users

  • Organizations can start connecting their own Shopify stores without manually pasting private store tokens.
  • PageCRM is ready for the next Shopify phase: product, customer, order, and webhook sync.
  • The integration follows the same organization-safe SaaS model used for other OAuth connections.
v1.1.32026-05-13

Indexing reliability and prepared mobile sign-in

PageCRM improved the reliability of Google indexing submissions for eligible public pages and prepared mobile OTP sign-in for a controlled future rollout.

What changed

  • Prepared Firebase mobile OTP sign-in behind a disabled feature flag for future testing.
  • Kept mobile OTP hidden from the public login page until rollout is approved.
  • Kept mobile OTP limited to existing users whose verified phone number is already saved on their PageCRM profile when the feature is enabled.
  • Improved Google indexing credential selection so the verified Search Console account is used automatically.

What this means for users

  • Users continue to see the existing email, Google, and GitHub sign-in options.
  • Organizations keep the same workspace security model because phone login only opens the matched existing account.
  • Eligible career pages can be submitted to Google indexing more reliably.
v1.1.22026-05-12

Mobile app installation and AI documentation improvements

PageCRM improved the mobile app installation experience and added clearer AI-readable documentation for MCP server capabilities.

What changed

  • Made the PageCRM install prompt available across public pages, login flow, and the logged-in workspace.
  • Added a direct Install PageCRM action on the install guide page for supported browsers.
  • Improved fallback instructions for iPhone, Android, Chrome, Edge, and desktop browsers when a native install prompt is not available.
  • Added structured MCP documentation so AI systems and support teams can understand available MCP tools, resources, prompts, and safety rules.

What this means for users

  • Mobile users have a clearer path to install PageCRM as a PWA.
  • Teams can find install guidance before and after login.
  • AI and support documentation is easier to discover and keep current.
v1.1.12026-05-04

Workspace speed and commerce connection improvements

PageCRM is now faster across daily work areas and easier to connect with Google Merchant Center for organization product catalog syncing.

What changed

  • Improved dashboard and pipeline responsiveness for faster daily review.
  • Made stage changes feel smoother when moving contacts through the sales process.
  • Improved contacts and product search behavior so lists feel more responsive while typing.
  • Made inbox loading more predictable and reduced unnecessary waiting during normal use.
  • Improved Google Merchant Center setup so one organization connection can support catalog sync for the team.
  • Added an option to create a PageCRM product data source directly from the Merchant Center setup screen.
  • Added performance improvements for larger workspaces with more contacts, products, and messages.

What this means for users

  • Teams can move through core CRM screens with less waiting.
  • Sales and operations users can update pipeline stages, search records, and review messages more comfortably.
  • Commerce teams can connect Merchant Center with fewer setup steps and keep catalog-ready products moving toward Google.
  • Larger organizations should see a better experience as data volume grows.
v1.0.12026-04-23

Help center, release tracking, and clearer product visibility

PageCRM added a public help center, a public release log, and clearer version visibility so teams can understand product changes more easily.

What changed

  • Added a public help center for setup, inbox, contacts, billing, mobile app, and troubleshooting guidance.
  • Added a public releases page that explains product updates in plain language.
  • Showed the current app version in the public footer and inside the logged-in app.
  • Added footer and navigation links so users can reach help and release notes from common areas.

What this means for users

  • Users can see what version they are using and where to read what changed.
  • Support and onboarding can point users to stable public guidance.
v1.0.02026-04-22

Mobile app experience and communication foundation

PageCRM improved its installable app experience, notifications, inbox usability, and branded mailbox foundation for daily CRM work.

What changed

  • Improved the mobile-friendly app experience for users who install PageCRM on their device.
  • Improved inbox usability, older message access, and mobile presentation.
  • Improved branded mailbox access for PageCRM mail users.
  • Improved sender-domain setup guidance for organizations.

What this means for users

  • Teams can use PageCRM more comfortably on desktop and mobile.
  • Organizations have a stronger foundation for email, inbox, and sender setup workflows.

Need setup guidance instead of release notes?

Use the help center when you need step-by-step product guidance. Use this page when you need to understand what changed between versions or whether a workflow was updated.