Things to check after this release
- Accounting customers: the first push is manual. Confirm the company/provider link before invoicing. Reconnect older Xero connections to use full sync.
- Invoice delivery: review who sends the email before releasing a batch. Microsoft 365 needs permission to send from the selected mailbox; a billing email address alone does not provide that permission.
- Alternative Payments: use one route for each invoice. If direct sending was enabled and an invoice was voided or marked paid from October 20 until the October 30 fix, check AP for part payments and missing receipts; those historical cases are not all repaired automatically.
- Permissions: review technician shared-vault access and add new API scopes deliberately. Existing API keys do not gain the new scopes automatically.
Ticketing and routing
- Technician groups and queues: keep work in a group without assigning an individual, or use round-robin and fewest-open assignment.
- Routing controls: technician availability, primary-technician preference, overflow groups and support tiers.
- Distribution report: see why assignments were made and release selected work back to its queue after confirmation.
- Custom ticket statuses: define statuses within the fixed lifecycle categories, with customer-facing labels, required reasons, pause behavior and reply rules.
- Unassigned filters: combine unassigned work with company and group views.
- Notifications: group targeting and an inbox of unread assignments, mentions, customer replies and ticket alerts. Unanswered-work alerts can use business time or 24/7 thresholds.
- Reply handling: genuine linked customer replies reopen resolved or closed work across supported channels; automatic replies do not reopen tickets.
- Fixes: changing a ticket’s contact updates its requester, technician pickers work for the appropriate roles, and policy/SLA notifications no longer remain unread after being read.
Service levels
- Business and on-call calendars, holidays, ordered policy matching and separate response/resolution coverage.
- Escalation levels: per-metric actions, events and automation conditions, checked every minute with a backstop.
- Internal group targets: track pickup and resolution within a technician group.
- SLA details on tickets: inspect clocks, targets and escalation actions.
- More accurate reporting: corrected reopened-ticket scoring, pause time and business-hours calculations. Recorded breaches are retained, and unchanged policy matches do not move deadlines.
- Intake fixes: eligible tickets receive their SLA through the shared creation path; recurring tickets stay out of client SLA reports. Bot intake asks urgency rather than allowing requesters to choose Critical priority.
Customer requests and automations
- Request catalog: customer forms with company/role audiences, conditional fields, urgency wording and requests on behalf of colleagues.
- Multi-level approvals: ANY/ALL decisions, expiry and fallback handling, including portal approvals.
- Fulfilment plans: internal task tickets with dependencies, date-based release and approval gates. Customers see parent-request progress while internal tasks stay private.
- Portal home: configurable tiles and wording. The catalog stays off until enabled.
- Automation rules: typed custom-field conditions, group assignment, routing, tier escalation and checklists.
- Test and execute: select a ticket explicitly for testing, execute a saved rule now, or preview and run it against all matching tickets. Enabling a rule does not replay existing tickets. A failed action stops later actions without undoing earlier successes.
Reporting, import and the API
- Daily ticket ledger and lifecycle history, with recorded history distinguished from older reconstructed data.
- Exports: choose columns, save definitions and schedule repeat exports.
- Public PSA API: ticket lists, reads, updates and assignment; history and change feeds; directory, queue and time reads alongside note/time writes.
- API reliability: clearer validation, idempotency behavior and permission errors while preserving existing-key compatibility.
- Outbound webhooks: Standard Webhooks signatures, longer retries, immediate secret rotation and delivery resend controls. Delivery tracking avoids repeating work for endpoints that already received it.
- Import fixes: improved ServiceDesk Plus ticket/history compatibility and bounded product imports.
- API service accounts no longer consume a PSA seat.
Billing, invoices and agreements
- Saved invoice drafts: return to unfinished work and preview the current PDF before issuing an invoice.
- Review and release: opt clients into approval before sending or syncing, release batches of up to 25 invoices, and resume partial failures with individual errors preserved.
- Client financial preferences: billing names, structured addresses, payment terms, due-date rules, PO/reference and presentation defaults. A due date does not enable autopay.
- Product descriptions: create products inline, edit long descriptions in an expanded editor, and preserve headings and negotiated rates on invoice lines.
- Invoice email controls: choose Regentra, a Microsoft 365 mailbox, Stripe or QuickBooks as the delivery owner for reviewed releases. Preview the sender, recipient and subject; configure Reply-To, PDF attachment and payment-link options for native email.
- Invoice designs: Classic (formerly Service details), Modern, Minimal, Bold and the original Standard layout. Choose an organization default, client layout, accent colour, paper size, wording and visible columns, with a sample preview.
- PDF presentation: payment instructions beside totals in Classic, a configurable page footer, and page numbers only on multi-page invoices. Saved organization design controls also affect later downloads of older invoices that use them.
- Agreements: preserved product links and negotiated prices, validated service periods, recurring-item imports and optional billing schedules. Only applicable uncovered charges are billed; resuming does not bill every missed month automatically.
- Settlement fixes: provider identities, split payments, retry handling and collection-close warnings stay consistent. A local Paid status does not prove every remote action succeeded.
Quotes and products
- Preview before saving: inspect the quote PDF before Create Quote, or preview unsaved edits on an existing quote, without creating or sending it.
- Notes and terms on the creation form, with the organization’s default terms prefilled for new quotes. Notes print on the customer’s quote.
- Acceptance block: signature lines on eligible unsigned quotes and recorded acceptance details after acceptance.
- Products on quote lines: pick a USD product to fill description, price and default cadence, or explicitly save a new line to Products. Product links carry through cloning and invoice conversion.
- Quote cadence on products and CSV import/export. It prefills a quote line; it does not start recurring billing.
- Safer sends: duplicate clicks and retries no longer create competing quote sends or invalidate a newer resend link.
Accounting and payment integrations
- Zoho Books: customer and item linking, invoice import and company matching, with explicit controls for product ownership and invoice sending where the integration is enabled.
- Xero: full-sync setup and mapping, with reconnection needed for older connections.
- QuickBooks: optional item and invoice import, product-specific invoice items, customer billing-name updates and clearer mapping behavior.
- Provider-change review: inspect accounting-side voids and deletions before applying them locally. Monthly-agreement delivery and other automatic sends have separate controls.
- Connection setup: settings open in a side panel, errors explain the cause, and switching accounting providers requires confirmation.
- Alternative Payments setup: Production/Demo selection persists, saved keys remain write-only, and connection tests time out without losing entered values.
- AP payments: corrected balance handling after AP changed its API, restoring part-payment detection and split settlement. Refund and notification recovery checks use confirmed provider records.
- Regentra PDFs in AP: an optional QuickBooks accounting-route workflow replaces the PDF on AP’s existing invoice using verified QuickBooks tax and totals. It starts with new eligible invoices; older open invoices can be uploaded individually. Direct sending, Xero and Zoho are outside this PDF workflow.
Calendar, companies and branding
- Customer appointments: invite several technicians, schedule repeating meetings, and open or edit an existing appointment.
- Company workspaces: reorganized details, inline contacts, managers, portal roles, primary-contact filters and a star for primary contacts.
- Branded sign-in: password pages keep the sign-in link’s address and use readable brand colours.
- Trials: the seven-day extension is offered with two days remaining, with clearer billing-start wording when buying during a trial.
- MSP plan prices display in the correct units.
Sign-in and password vault
- Active sessions: review sign-ins and end one session, other sessions or all sessions.
- Session policies: inactivity and maximum lifetimes, remembered-account/device controls and coordination across tabs.
- Recovery and alerts: backup codes for passkey-only accounts, new-browser sign-in emails and increasing waits after repeated password failures.
- Authenticator choice: setup prominently offers an authenticator app or a passkey. Standard authenticator codes work independently of a Microsoft directory connection.
- Continue with Microsoft can complete eligible password sign-ins even with organization SSO off, when the account’s trusted directory and Microsoft’s MFA proof match. A failed account lookup offers the account chooser on retry.
- Tenant lockout recovery: platform support has a verified reset path when the only tenant account cannot reach its factors.
- Vault access: separate technician permissions, named-person visibility, visible notes, share revocation after a password change and a 30-day restore window.
- Vault authenticator codes, where enabled: setup-key or QR-image import, code preview before saving, and a recent identity check before code generation. QR images are read on the device. Keep Regentra’s own sign-in factor and backup codes separate from the vault.
Compliance, security and reliability
- CIS Controls and Microsoft 365 Benchmark profiles, with scoped adoption and partial evidence coverage where a full assessment is not possible.
- Policy template review: compare and adopt updates deliberately. Material changes to approved/active policies create a new draft for approval; acknowledgment campaigns remain separate.
- Policy documents: repaired images and links across editing, review, signing, printing and PDF export.
- Client switching: compliance clients remain listed after moving from PSA.
- MSP separation: a client administrator can end management with confirmation and a recent identity check. Eligible MSP-provided products receive a 14-day transition window; former-MSP access and feeds are cut off.
- Security fixes: stronger attachment and tenant authorization, Microsoft identity checks, private customer AI evidence, integration-secret handling and protection against abusive requests.
- Email and chat: improved screenshot imports, reply threading, fairer inbound processing across organizations and prevention of chat-bridge loops.
- Everyday fixes: a deliberately selected 09:00–09:30 time entry can be saved; certification reminders and staff ticket emails open the right destination; SMS retries do not duplicate replies or reopen notifications.
- Under the hood: patched dependencies and runtime, stronger release checks and migration validation, and further tenant-isolation groundwork. Features still behind disabled rollout controls are not enabled by these notes.