Tell us how we could make the product more useful to you. We URGE you to use the Pelcro Discovery GPT to help structure your thoughts and recommend a feature request that will be quickly digested by our team!
Have something to say?
Add Bill To "Company" and "Department" to the invoice export
🔍 Problem Statement The invoice export doesn’t include the Company and Department from the billing address, so publishers who mail invoices have to combine it with the address export before running a mail merge. 💡 User Story As a business owner, I want the invoice export to include the Bill To Company and Department, so that I can produce mailed invoices and renewal notices from a single file. 🎯 Definition of Done (DoD) ✔ The invoice export includes Bill To Company and Bill To Department columns, taken from the billing address on each invoice. ✔ Invoices without a company or department show a blank value without breaking the export. ✔ Existing columns in the invoice export stay unchanged.
Planned
AI Agent: Allow clients to query errored Open API requests
🔍 Problem Statement As a client admin, I can only find errored API requests by searching Settings > Logs > Open API by hand, which results in avoidable support tickets. 💡 User Story As a client admin, I want to ask the Pelcro AI Agent for errored API requests by customer, endpoint, response code or date, so that I can diagnose failures without contacting support. 🎯 Definition of Done (DoD) Given a site with errored Open API requests (4xx or 5xx), when an admin calls [clarify endpoint, e.g. GET /api/v1/core/logs/open-api] with a date range, then it returns only that site's errored requests. Given filters (customer ID, request URI, response code, report_id), when applied, then each result matches them and shows the timestamp, request URI, response code, error and customer ID. Given an admin asks the AI Agent "show 422 errors from the last 7 days", when it answers, then it lists the matching requests and their total count. Given a user without the admin role, when they ask the AI Agent or call the endpoint, then the request is refused. Given the release, then the endpoint is documented on docs.pelcro.com and covered by automated tests, and it is exposed as an MCP tool with at least one eval. This change will impact the API and Integration layers, specifically a new Core API logs endpoint, a new MCP server tool and the AI Agent (/admin/ai-agent/chat). This solution will include the following limitations: read-only; errored Open API requests only, no successful requests; no real-time alerts; no errors from custom client UI flows or from payments the gateway rejects before they reach Pelcro; history limited to log retention [clarify]; request payloads excluded [clarify].
Planned
Pelcro Autocapture: paywall conversion tracking
🔍 Problem Statement As a publisher, I can't see where readers drop off in the paywall flow, which limits my ability to improve subscription conversion. 💡 User Story As a publisher, I want paywall interactions captured automatically, so that I can find and fix conversion drop-offs without custom tracking code. As a Pelcro product team member, I want a standard paywall event schema, so that conversion analysis is consistent across clients and analytics tools. As a Pelcro AI harness, I want documented instructions for every event and property, so that I can interpret paywall behavior and help improve conversions for clients. 🎯 Definition of Done (DoD) ✔ Given a paywall renders, when a reader interacts with it, then the SDK emits the standard events defined in the Event Definitions below. ✔ Given any event, when it is sent, then it carries the common properties defined below. ✔ Given a reader identifies or subscribes, when the event fires, then the anonymous ID merges with the known customer ID. ✔ Given a reader has not consented, when the paywall renders, then no events are emitted or identifiers stored. ✔ Given a client, when it calls the events API [clarify endpoint], then it receives paywall funnel conversion by step, variant, and source. ✔ Given the event schema, when the AI harness loads its instructions, then it receives a definition of every event and property, so it can analyze paywall funnels and recommend conversion improvements. ✔ This change will impact SDK, UI, and API, specifically JS-SDK event tracking, ReactJS Elements paywall components, and [clarify events API endpoint]. ✔ This solution will include the following limitations: no session replay; no capture of form input values or personal data; sites not using the Pelcro paywall excluded; [clarify scroll depth and rage-click scope].
Planned
Introduce automation signals in Customer Activity and Customer view
🔍 Problem Statement As a publisher reviewing Customer Activity, I cannot tell which events came from automated browsers, which results in bot traffic reading as reader behaviour in the event feed and in each customer's history, with no way to isolate it. 💡 User Story As a publisher, I want events from automated browsers marked in Customer Activity, so that I can recognise bot events in the feed and in event details. As a publisher, I want to filter Customer Activity by automation, so that I can isolate or exclude bot traffic. As a publisher, I want a notice on a customer's page when their recent events came from an automated browser, so that I can spot accounts used by scripts or scrapers. 🎯 Definition of Done (DoD) A feature is done when: ✔ Given an event with browser.webdriver = true or at least one value in browser.headless_tells, when it shows in the Customer Activity feed, then the row has an "Automation" badge. [clarify: is one headless tell enough, or should it require webdriver = true or 2+ tells?] ✔ Given that event, when its detail panel opens, then Device & Browser shows "Automation: Yes" and lists the signals found (webdriver, each headless tell). ✔ Given an event with both fields present and neither signal, when it shows, then it has no badge and the panel shows "Automation: No". ✔ Given an event sent by an SDK older than v4.6.1 (fields absent), when it shows, then it has no badge and the panel shows "Automation: Unknown". ✔ Given the Customer Activity filters, when the publisher sets Automation to Automated, Not automated or All, then the feed, the event count and the export return only matching events. Not automated includes Unknown events. The default is All, so current results do not change. ✔ Given a customer page, when it loads, then a background request counts that customer's automated events in the last 30 days, and the page renders without waiting for it. ✔ Given that count is 1 or more, when the request returns, then the page shows "Likely accessed via automation" with the count and the date of the last automated event, linking to the customer's Activity tab filtered to Automation = Automated. ✔ Given that count is 0, or the request fails or times out, when the page loads, then no notice is shown and the page works as before. ✔ This change will impact the UI, specifically the Customer Activity feed, event detail panel and filters (Publisher\CustomerActivityController, CustomerActivityFacetService, CSV export) and the customer page (Publisher\CustomerController). ✔ This solution will include the following limitations: only browsers that expose automation (webdriver, headless tells) are flagged; stealth automation and non-browser scripts are not; sites on SDKs older than v4.6.1 show Unknown; data covers the 30-day retention window only; the overview cards and funnel still count all traffic; the Core API and MCP analytics are not changed; nothing is blocked.
Planned
Organization ticket digest: email client contacts their organization's open tickets
🔍 Problem Statement As a client contact, I can't see my organization's open support tickets in one place, so I chase status updates ticket by ticket. 💡 User Story As a client contact, I want a scheduled email listing my organization's open tickets and their status, so that my team knows where every request stands. As a support admin, I want to send that email from an Automation targeting a customer segment, so that adding a contact to an organization enrolls them. 🎯 Definition of Done (DoD) Audience Given an Automation with only the Send email action, when an admin picks customer segments as its audience, then it saves without the Creation action. Given that Automation runs, when recipients are selected from its customer segments, then each matching customer gets one email and no subscription is created. Given the customer segment builder, when an admin adds an Organization criterion (has any organization, or is one of selected organizations), then only matching customers are included. Email content Given an email containing {{organization.open_tickets}}, when it is sent, then it lists the recipient's organization's unsolved tickets on the Automation's site with ID, subject, status and last activity. Given any listed ticket, when it is rendered, then its status reads Open (New, Active, On hold) or Awaiting your reply (Pending). Given a ticket subject containing markdown or HTML, when it is listed, then it renders as plain text. Given an email containing {{organization.name}}, when it is sent, then it shows the recipient's organization name. Given a recipient whose organization has no unsolved tickets, when the Automation runs, then [decision: skip their email, or send a "no open tickets" message]. Ticket linking Given unlinked tickets opened from an email address, when a customer with that address is created on the same site, then those tickets link to the new customer. Given existing unlinked tickets, when the one-time backfill runs, then every ticket whose first inbound sender matches a customer on its site is linked to that customer. Given a ticket in the dashboard, when an agent picks a customer in the ticket details, then the ticket links to that customer, including re-linking a wrong match. Given a request that sets a ticket's customer, when it is saved, then only a customer on the ticket's site is accepted. Given a customer who moves to another organization, when the digest runs, then [decision: their past tickets stay with the old organization, or move with them]. Security and API Given a visitor registering through the SDK on the support site [decision: or every Ticket Center site], when they enter an existing organization's name, then they are not added to it. Given the new Core API endpoint for linking a ticket to a customer, when it is released, then it is documented on docs.pelcro.com and covered by automated tests. This change will impact the UI and API, specifically Automations (campaign form and Initiate job), customer segments, the email variable catalog, ticket linking and SDK registration. This solution will include the following limitations: weekly read-only snapshot; no replies or new tickets from the digest; unsolved tickets only; one organization per contact; contacts must be customers on the support site, loaded separately through the Core API; no Core API for creating Automations or segments.
Planned
Enhance AI Agent Customer Activity Insights Through a Dedicated Core API Endpoint
🔍 Problem Statement Currently, Pelcro's AI Agent has limited context about Customer Activity, preventing admins from asking detailed questions or performing deeper analysis of customer behavior. A dedicated Core API endpoint is needed to provide the AI Agent with access to Customer Activity data, scoped by site and account. 💡 User Story As a Pelcro admin, I want to ask the AI Agent detailed questions about Customer Activity, so that I can better understand customer behavior, engagement, and trends without manually analyzing the data. 🎯 Definition of Done (DoD) 1. Dedicated Customer Activity Endpoint Develop a dedicated Core API endpoint for retrieving and analyzing Customer Activity data. Ensure the endpoint is scoped by Site ID and Account ID, respecting existing access permissions. Support filtering by relevant activity types, date ranges, customers, and other available attributes. 2. AI Agent Integration Expose the endpoint through the necessary MCP tools for AI Agent consumption. Allow the AI Agent to retrieve sufficient context to answer detailed Customer Activity questions. Support follow-up questions and deeper analysis based on the retrieved data. 3. Customer Activity Insights Enable questions such as: Which pages generate the most customer engagement? What are the most common customer activities over the last 30 days? Which referral sources drive the most customer activity? How has customer engagement changed over time? Ensure responses are based on actual available Customer Activity data. 4. Performance and Security Optimize the endpoint for efficient data retrieval, filtering, and aggregation. Avoid unnecessarily large responses that could impact AI Agent performance. Enforce site- and account-level data isolation and permissions. ✅ Expected Outcome The AI Agent can answer detailed, contextual questions about Customer Activity using accurate, site- and account-scoped data, enabling publishers to gain deeper insights into customer behavior and engagement.
Planned
Ticket Center: auto-mark Urgent/Priority subjects as Urgent and email all collaborators
🔍 Problem Statement As a support agent, I set ticket priority by hand and only see new tickets inside the Ticket Center, so urgent requests wait unnoticed. 💡 User Story As a support agent, I want tickets whose subject contains "Urgent" or "Priority" marked Urgent on creation, so that they stand out without manual triage. As a support team, I want every collaborator emailed when a new Urgent ticket arrives, with subject, description, sender and priority, so that we respond without watching the Ticket Center. 🎯 Definition of Done (DoD) Given a new ticket from any source, when its subject contains the whole word "urgent" or "priority" in any case, then its priority is set to Urgent. Given an agent picks a priority when creating a ticket in the dashboard, when the subject contains a keyword, then the agent's priority is kept. Given a site admin in Ticket Center settings, when they turn urgent ticket emails on or off, then the setting is saved; it is off by default. Given the setting is on, when a ticket is created as Urgent, by an agent or by the keyword rule, then each active collaborator on the site gets one email with subject, description, sender, priority and a ticket link. Given the setting is on, when a ticket is created with any other priority or none, then no email is sent. Given a collaborator who is deactivated or has not accepted their invitation, when an Urgent ticket is created, then they get no email. Given a ticket with a linked customer or an inbound From address, when the email is sent, then the sender shows that name and email; otherwise it reads Unknown. Given a collaborator replies to the alert email, when the reply arrives, then no new ticket is opened and nothing reaches the customer. Given SendGrid re-delivers an inbound email that already opened an Urgent ticket, when it is processed, then no second alert email is sent. Given the email to one collaborator fails, when an Urgent ticket is created, then the ticket is still created, the other collaborators still get theirs and the failure is reported to Sentry. Given an API user, when they call GET or PATCH v1/core/ticket-settings (proposed, modeled on v1/core/email-settings), then they can read and update the urgent ticket email setting. Given the keyword rule and the new endpoint, when they are released, then they are documented on docs.pelcro.com and covered by automated tests. This change will impact the API and UI, specifically ticket creation (InboundTicketFactory, Publisher TicketController@store), a queued collaborator email, Ticket Center settings and a new v1/core/ticket-settings endpoint. This solution will include the following limitations: keywords fixed to "urgent" and "priority", not configurable per site; whole words only, so "urgently" and "prioritize" do not match; subjects such as "Low priority question" are also marked Urgent; the keyword rule runs on creation only, not on subject edits or replies; never overrides a priority already set; only tickets that are Urgent when created trigger an email, so raising a ticket to Urgent later does not; Voice AI tickets never trigger an email because they are created without a priority and with a generated subject; one site-wide setting, no per-collaborator opt-out or digest; ticket attachments are not included in the email; [decision: every Ticket Center site, or site 5781 only].
Planned
Support Paywall Creation Through AI Harness
Title: Support Paywall Creation Through AI Harness 🔍 Problem Statement Currently, creating a paywall in Pelcro requires admins to complete a lengthy configuration form with multiple settings and targeting options. This makes the process time-consuming and complex. To simplify paywall creation, Pelcro should support creating and configuring paywalls conversationally through the AI Harness. 💡 User Story As a publisher admin, I want to create and configure paywalls using natural-language prompts through the AI Harness, so that I can set up paywalls quickly without manually completing the entire creation form. 🎯 Definition of Done (DoD) 1. AI-Powered Paywall Creation Allow admins to create paywalls through natural-language prompts in the AI Harness. Enable the AI Harness to interpret and configure the required paywall settings, targeting rules, and behavior based on the admin's instructions. Ask for clarification when required configuration details are missing. 2. MCP Tools and Core API Endpoints Develop or extend the necessary MCP tools and core API endpoints to support paywall creation and configuration. Ensure all relevant paywall creation fields and targeting attributes are supported. Apply the same validation rules and permissions as the existing paywall creation form. 3. Review and Confirmation Display a summary of the generated paywall configuration for the admin to review. Allow admins to request modifications through follow-up prompts. Require explicit admin confirmation before creating or activating the paywall. 4. Compatibility Ensure paywalls created through the AI Harness are saved and displayed correctly in the existing Paywall Management UI. Preserve the existing manual paywall creation functionality. 🔧 Impacted Components AI Harness MCP Server and Tools Core Paywall API Endpoints Paywall Creation and Configuration Paywall Management UI ✅ Expected Outcome Publisher admins can create and configure paywalls through conversational prompts, reducing manual setup effort while maintaining consistency with Pelcro's existing paywall functionality.
Planned
Add Referrer-Based Targeting to Paywall Configuration
🔍 Problem Statement Currently, Pelcro's paywall configuration does not support targeting visitors based on their referral source. This limits publishers' ability to customize paywall behavior depending on where visitors are coming from. 💡 User Story As a publisher admin, I want to configure paywall targeting based on the visitor's referrer, so that I can display different paywalls to visitors coming from specific websites or traffic sources. 🎯 Definition of Done (DoD) 1. New Referrer Targeting Attribute Introduce a new Referrer attribute within the paywall targeting configuration. Allow admins to specify one or multiple referring domains or URLs (e.g., google.com, facebook.com). Support expressions in the input field like *.google.com. Support including or excluding specified referrers. 2. Paywall Targeting Logic Given a visitor arrives from a configured referrer, display the corresponding paywall when all other targeting conditions are met. Given a visitor does not match the configured referrer, do not trigger that paywall based on this rule. Handle visitors with missing or unavailable referrer information. 3. Compatibility Ensure referrer targeting works alongside existing paywall targeting attributes. Preserve existing paywall behavior for configurations that do not use referrer targeting. Support the new attribute through the UI and API. 🔧 Impacted Components Paywall Configuration UI Paywall Targeting Logic Paywall API ✅ Expected Outcome Publishers can target visitors with specific paywall experiences based on their referral sources, enabling more personalized paywall strategies.
Planned
Add line-level VAT fields to a new invoices export
🔍 Problem Statement As an EU finance user, I cannot prepare VAT reports from the invoices export, because it lacks VAT rate, VAT type and product code per line. 💡 User Stories As a finance user, I want a new invoices export to show one row per invoice line with its VAT data. As a finance user, I want credit note, refund and discount rows to reference the original invoice and its quarter, so that VAT returns correct the right period. As a finance user, I want customer type and VAT ID on each row, so that the ZM can be derived from the same export. 🎯 Definition of Done Add a new export for this enhancement (extension of invoices). Given an invoice for a bundle plan, when exported, then each product and postage charge is a separate row with its own net amount, VAT amount and rate. Given a credit note, refund or discount, when exported, then each row includes its own document number, the original invoice number and date, and the original reporting quarter. Given a selected quarter, when the export is filtered to EU consumer lines, then it matches the OSS Individual Transactions report. Given an invoice, when requested via [clarify endpoint, e.g. GET /invoices/:id], then the API returns the same line-level fields. This change will impact the API and export layers, specifically the invoices export and invoice line items.
Add a Segment filter for current invoice amount
🔍 Problem Statement As a publisher, I can't segment subscriptions by the price they currently pay: the Price filter matches any past invoice, and the Plan amount filter checks the plan price only, ignoring coupons, so renewal segments overlap or target the wrong price. 💡 User Story As a publisher, I want a new segment filter that checks only the amount of the subscription's current invoice, so that I can target renewal offers by the price each subscriber currently pays. 🎯 Definition of Done (DoD) A feature is done when: ✔ When the user adds the current invoice amount filter in the segment, then only subscriptions whose current invoice matches are included, regardless of past invoices. ✔ The filter matches the invoice amount after coupons and discounts. ✔ The filter supports an exact amount or a range, like the Price filter.
Done
Add First and Last Name to Membership Export
Summary We’d like to request that the membership export include first name and last name as separate columns alongside the existing email address field. Business Need Our team regularly exports membership lists to share with customers for list cleanup and verification. Currently the export only includes email addresses, which makes it difficult to identify individual members — especially when email formats use variations like first-initial-last-name (e.g., jsmith@company.com). Having the first and last name broken out separately would make these exports immediately usable without additional manual lookup. We also want to note that the customer member search isn’t a reliable alternative for this, as many customers have multiple domains associated with their license. Searching by domain doesn’t capture the full picture, so the membership export is the primary tool our team relies on. Steps to Reproduce Current Workflow Navigate to a membership (e.g., https://www.pelcro.com/admin/5118/subscription/2295136/members) Click Export Receive the exported report — currently includes email address but does not include first name or last name Requested Enhancement Add two additional columns to the membership export: First Name Last Name These should appear as separate fields alongside the existing email address column. Expected Outcome When a team member clicks Export on a membership, the downloaded report includes first name, last name, and email address for each member, making it easier to identify individuals and share clean lists with customers. Thank you for considering this enhancement. Example export missing the name fields and cut off organization field.
Subscription purchase prevention logic
🔍 Problem Statement As a subscriber, I get no warning when I buy a second subscription to a product I already have, so I get charged twice. 💡 User Story As a subscriber, I want a warning before I buy a product I already subscribe to, so that I don’t pay twice for the same access. As a subscriber, I want a Renew option in that warning, so that I can extend my current subscription instead of buying a new one. As a publisher, I want to turn this check on per site, so that sites that sell several subscriptions per customer keep working. 🎯 Definition of Done (DoD) ✔ Given the setting is on and the customer has a current subscription to product A, when they start checkout for any plan of product A, then the prevention modal displays. ✔ Given the customer’s current subscriptions are all to other products, when they start checkout for product B, then checkout continues with no modal. ✔ A current subscription is active, in a free trial, or extended. Donations and gifts bought for someone else do not count. ✔ Given the modal displays, when the customer clicks Renew, then they go to the renewal checkout for their current subscription [clarify: renew on the plan they selected or the plan they have]. ✔ Given the current subscription cannot be renewed, when the modal displays, then the Renew option is hidden. ✔ Given the modal displays, when the customer closes it, then no subscription or charge is created. ✔ Given the setting is on, when a purchase request for a product the customer already has reaches Pelcro by any route, then Pelcro blocks it. ✔ The setting is off by default, so existing sites keep today’s behavior. ✔ The setting and the new purchase rule are documented on docs.pelcro.com and covered by automated tests.
Make the minimum password length configurable
🔍 Problem Statement As a publisher, I can't configure the password character requirement for my site. On the FAD microsite it is currently set to 15 characters. 💡 User Story As a publisher, I want to configure the minimum number of password characters for my site, so that it fits what we want for our users. 🎯 Definition of Done (DoD) A feature is done when: ✔ Given a publisher sets the minimum number of password characters for their site, when a customer creates or changes a password, then the password must meet that minimum. ✔ Given a publisher has not changed the setting, when a customer creates a password, then the current requirement still applies.
Disable Gift Creation in the Customer Portal
🔍 Problem Statement Publishers who no longer offer gifting can hide the gift option during plan selection and checkout, but customers can still create new gifts through the customer portal (Gifts > Add a gift). 💡 User Story As a publisher, I want to disable gift creation across all entry points, including the customer portal, so that customers can’t create new gifts while still having access to their existing ones. 🎯 Definition of Done (DoD) ✔ Gift creation can be disabled in the customer portal (Gifts > Add a gift). ✔ Direct access to the gift creation flow is blocked when gift creation is disabled. ✔ Existing gifts, including recipient details and shipping addresses, stay accessible to customers. ✔ This change will impact UI, specifically the Gifts section of the customer portal and the gift creation flow.
In Progress
Allow pinning Default UI Version to the newest release without automatic upgrades
🔍 Problem Statement As a site admin, I can only adopt the newest UI version by selecting "Latest," which results in automatic future upgrades without consent. 💡 User Story As a site admin, I want to pin my site to the newest UI version, so that I get current features without automatic future upgrades. As a site admin, I want "Latest" to remain available, so that I can still opt into automatic upgrades. 🎯 Definition of Done (DoD) ✔ Given the Default UI Version setting, when an admin opens the dropdown, then the newest release (currently 3.0) is listed as a pinnable option separate from "Latest (3.0)". ✔ Given a site pinned to 3.0, when a newer UI version is released, then the site continues serving 3.0 until an admin changes the setting. ✔ Given a site set to "Latest", when a newer UI version is released, then the site serves the new version, unchanged from current behavior. ✔ Given a new UI version is released, when it is published, then it appears in the dropdown as a pinnable option without manual configuration. ✔ Given a site settings API request, when the UI version is read or updated, then the API accepts and returns either a specific version or "latest". ✔ This change will impact UI, API, and SDK, specifically the Site Settings Default UI Version dropdown, [clarify site settings endpoint/field], and the UI bundle version loader. ✔ This solution will include the following limitations: no notification of new UI releases; no automatic migration of existing "Latest" sites to a pinned version; no per-page or per-environment version selection.
In Progress
Utilization2: Optimize AI Home recommendations
🔍 Problem Statement Currently, the Pelcro homepage provides business performance insights and AI-powered recommendations, but these do not fully leverage the customer activity data already available within Pelcro. Clients can access information about customer behavior, traffic sources, page visits, and device engagement, but may not know how to interpret this data or use it to improve conversions and revenue. Additionally, homepage recommendations should do more than promote unused Pelcro features. They should proactively identify meaningful business opportunities, explain their potential impact, and guide clients toward actionable next steps using AI Harness or relevant Pelcro functionality. 💡 User Story As a Pelcro admin, I want to receive personalized, actionable AI-powered recommendations on my homepage based on my account activity, customer behavior, business performance, and feature utilization, so that I can identify revenue opportunities, understand customer engagement, and discover relevant Pelcro features without having to analyze the data manually. 🎯 Definition of Done (DoD) 1. Homepage Recommendation Prioritization Given an account has urgent financial issues, such as significant revenue decline or past-due MRR, prioritize these insights over promotional recommendations. Given no urgent financial issues exist, prioritize relevant feature adoption opportunities and actionable customer activity insights based on their potential business impact. Given customer activity data indicates opportunities to improve conversions or revenue, prioritize those insights over lower-impact feature promotions. Given additional recommendations are available, display them below the top recommendations. Given a recommendation becomes irrelevant or its suggested action is completed, remove it and replace it with the next eligible recommendation. Avoid displaying multiple recommendations that communicate the same issue or opportunity. Recommended Sorting of Homepage Cards Priority Card Where to Display Reason 1 Identify High-Traffic, Low-Conversion Pages Top row Highlights opportunities to turn existing traffic into more subscriptions and revenue 2 Enable Apple Pay / Google Pay Top row Direct checkout improvement when supported but not enabled 3 Create Your Revenue Growth Plan Top row Drives AI Agent engagement and promotes AI Billing 4 Identify Your Top Referral Sources Second row, dynamically Helps clients understand which acquisition channels drive valuable traffic and conversions 5 Discover Your Top-Converting Pages Second row Helps clients identify which pages generate the most subscriptions and revenue 6 Analyze
In Progress
Utilization: Optimize AI studio recommendations
🔍 Problem Statement Currently, AI Studio displays a limited set of suggested prompts focused primarily on basic screen customization, such as changing brand colors, rewriting text, and modifying navigation. These suggestions do not fully demonstrate the potential value of AI Studio to clients, particularly when it comes to improving checkout conversions, reducing subscription cancellations, and enhancing the overall customer experience. We want to introduce more engaging, business-oriented predefined prompts that encourage clients to explore AI Studio and discover how they can customize their storefronts. 💡 User Story As a Pelcro admin, I want to see relevant, predefined prompts when opening AI Studio, so that I can quickly discover useful customization opportunities and make improvements without having to write prompts from scratch. 🎯 Definition of Done (DoD) 1. Add New Suggested Prompts Add the following predefined prompts to the Suggested section of AI Studio: Checkout Conversion Show a coupon when someone hesitates at checkout. Make my checkout buttons more eye-catching. Subscription Retention Offer a coupon before someone cancels their subscription. Highlight my most popular subscription plan. Product Layout & Design Display my products side by side instead of vertically. Add a "Most Popular" badge to one of my plans. Given an admin opens AI Studio, when the Suggested section loads, then the predefined prompts should be displayed as clickable suggestions. Given an admin clicks a suggested prompt, then the prompt should be automatically populated into the AI Studio conversation and submitted for processing. The admin should be able to modify or refine the requested changes through follow-up messages. Existing suggested prompts should remain available unless intentionally replaced.
In Progress
Support toll free numbers in iVR
Currently, Pelcro's Twilio integration does not support using toll-free phone numbers for IVR configurations. This limits clients who want to use toll-free numbers for customer support, particularly those who need to maintain existing customer-facing numbers or test their IVR before going live. 💡 User Story As a Pelcro admin, I want to configure toll-free phone numbers through Twilio, so that customers can reach the IVR using a toll-free number instead of a regular local number. 🎯 Definition of Done (DoD) 1. Toll-Free Number Support Support adding and configuring Twilio toll-free numbers for Pelcro IVR. Allow toll-free numbers to be assigned to the appropriate Pelcro account. Ensure the integration supports properly provisioned and eligible Twilio toll-free numbers. 2. IVR Call Routing Given a customer calls a configured toll-free number, route the call to the correct Pelcro IVR flow. Ensure existing IVR functionality works with toll-free numbers, including menu navigation and call transfers where supported. Ensure existing local phone number configurations remain unaffected.
In Progress
Add Total Draw, Full Bundles and Loose Copies per Carrier Route to Bundle Top
Problem Statement Delivery team need the copy count, full bundles and loose copies printed on each carrier route page of the Bundle Top PDF, so they can bundle a carrier's papers straight from the page. User Story As an admin, I want each carrier route page of the Bundle Top to show the route's total draw, full bundles and loose copies, so the bundling team knows exactly how many bundles and loose papers to prepare for that carrier. Definition of Done (DoD) Given a Bundle Top PDF is generated, each carrier route page shows Total draw, Full bundles and Loose copies for that route, clearly labelled together in the route header area. Full bundles and loose copies are calculated from the route's total draw (copies delivered this run, stops excluded) using the formula above. The bundle size is configurable per account, set from the same Pelcro admin Bundle Top settings that hold "Include all quantities" (BundleTopController / StoreBundleTopRequest), and defaults to 30 when not set. When the total draw is less than the bundle size, the page shows 0 full bundles and loose = total draw. The Unassigned appendix and route-less groups show the same three figures, or the figures are explicitly omitted there. Pick one and keep it consistent. Existing layout, row lists (starts/stops/paused) and per-route copy/delivery-point totals stay unchanged.