v54: clearer actions, lighter screens

Automatic contact and Quick activity search; password-first sign-in presentation; an Issue & Feedback Log; customer context and follow-up subjects in reminders; a quieter My Day and an eight-stage sales funnel using full authorised totals.

Calendar now requests its displayed date range and groups events once. Work tracker uses server-side search and 50-row pages. Read the performance findings and architecture plan. Twenty-million-record capacity has not been load-tested or certified.

DIGIVISTA CRM · v54 WORKSPACE EXPERIENCE

Clear next actions. Controlled feature access.

The full feedback register separates delivered changes, existing protections and work that needs a provider connection or a future release.

What changes for your team

Basic → Standard → Advanced → Enterprise controls available capabilities. Your security role and record scope still control what you can do and whose records you can see. Existing accounts retain their current features until an authorised administrator saves reviewed settings.

Security is included in every package. Package selection cannot create an external connection, grant Super Admin, approve a phone number, send a campaign or expand a provider’s database.

For a salesperson

Open My Day, inspect all stages, then use Follow-ups → Today. Open the customer, read Customer review, record the conversation and choose a next action. Use Not scheduled to find open leads with no next date.

For a manager

Use Leads → Open and the owner filter. Read qualification before progressing a deal. Record the Won/Lost decision. Use Delivery & collaboration for the work that follows a sale.

For an Admin

Open Packages & team labels. Review designation, team and assigned package. Team labels do not change rights. Use Master setup → Reporting managers for reviewed reporting assignments; use Access rights for security roles.

For a Super Admin

Change the company package only after reviewing staff packages. Save reviewed settings, then use View as user to test actual access. Return to your own account before changing configuration.

For a provider or caller

Keep using the provider or approved calling workspace. A package upgrade does not expand their record scope, approve contacts or bypass download limits.

Screen walkthroughs · fictional sample records

Find the next action

Fictional CRM Follow-ups screen showing day filters and unscheduled leads — 1. Choose the day bucket; Not scheduled finds open leads without a next date. 2. Review the owner and next follow-up before recording an outcome. The download uses these same filters.

Review package availability

Fictional Standard package preview showing included and unavailable features — 1. Package enabled means the package allows the feature; the user’s role and record scope must still allow the action. 2. Save only after reviewing the draft. Team and designation labels never grant access to additional customer records.

Full feedback and readiness register

Requirement	Status	What the user gets / remaining dependency
Consistent screen layout	Included in this version	Sticky application toolbar and Super Admin bar keep the sidebar offset occupied while scrolling. Stable scrollbar space reduces horizontal movement.
All/Open lead views	Included in this version	All, Open, Won and Lost filters work on server-side totals and matching exports. Open excludes closed stages.
Follow-up dates	Included in this version	All open, Overdue, Today, Tomorrow, Upcoming and Not scheduled. Date boundaries use IST; Overdue can overlap Today because a time today may already have passed.
Guided stages and optional demo	Included in this version	New → Contacted → Qualified → Demo / Discussion (optional) → Proposal → Negotiation → Won / Lost. Customer review explains the purpose and next action. Old records keep their stages.
Customer review	Included in this version	Stage explanation, owner, scheduled next action and source attribution explanation appear alongside the existing customer timeline.
Qualification	Included in this version	Need, service, budget, decision maker, budget position, expected close and optional demo outcome. Saving qualification does not automatically change a lead stage.
Closing reasons	Included in this version	Editing an existing lead into Won or Lost requires the customer decision. Quick activity updates keep their note or Lost reason as stage evidence. New historic imports retain the existing capture workflow.
Deal amount vs invoice	Existing + clarified	Deal value is estimated/agreed sales value. Billing is a separate linked invoice/payment view; Won is not a payment receipt.
Projects and meetings	Included / retained	Delivery & collaboration is separate from Daily sales. Projects are optional after Won; standalone internal projects remain possible.
Quick mobile activity	Included in this version	Mobile updates is presented as Quick activity update. Find customer → record outcome → stage → next follow-up. Manual calls are not automatically recorded.
Call outcomes	Included / retained	Quick updates and call desk accept Interested and Not interested as well as Connected, No answer, Busy, Wrong number and Callback requested. Approved-calling outcomes retain the existing richer options.
Package controls	Included in this version	Basic/Standard/Advanced/Enterprise company entitlement, staff ceiling and feature blocks. Server-side gates protect relevant direct module APIs and reports. Existing workspace defaults to Enterprise.
Team and designation	Included in this version	Staff package, team label and job designation are separate from security role. Team labels do not grant data access. Reporting managers remain the authoritative data-scope control.
Role / team record access	Existing protection retained	Admin and QA existing scopes, manager own/direct-report scope, salesperson own scope, caller approved queue and provider own supplied data remain enforced. A Business Head designation alone grants no additional rights.
Feature preview	Included in this version	Admin package matrix previews entitlement only. Existing Super Admin View as user tests actual effective role and record access in a read-only session with a return button.
Provider / owner / caller	Existing protection retained	Immutable import/source provenance identifies the provider. Sales ownership controls assignment. Calls are recorded against the caller without replacing provenance.
Customer upload and feedback	Existing	Provider workspace accepts own uploads, row feedback and own updated-data downloads. No sending or editing of other users’ records is granted.
Contact quality	Existing	Technical checks and manual channel approval stay separate. Format/MX checks do not prove a person owns a phone/mailbox. Unapproved phones stay out of the approved calling queue.
Export protection	Existing + retained	Filtered exports and role restrictions remain. Caller allowance and both required approvers remain unchanged. Packages cannot override export approvals.
Duplicate review / merge	Existing	Reviewed conflict handling and controlled merges remain. Do not use package assignment to reassign or merge customer records.
Consent and suppression	Existing	Do-not-contact, permission checks and unsubscribe/suppression continue to apply to connected sends. Importing data does not grant marketing consent.
Mailbox purpose	Included explanation; inbound setup still required	Recorded emails/messages and delivery statuses are linked to customers. Outbound SMTP and login OTP are verified. Live incoming replies require an installed and verified inbound bridge; a UI mailbox is not proof of reply capture.
BUSY automatic sync	Setup required	Billing bridge supports mapped references and sync status. The user deferred BUSY setup. Confirm edition, machine, supported export/API and secure bridge before a real automatic connection.
WhatsApp / telephony / SMS	Setup required	Provider accounts and approved templates/consent are required where applicable. No package selection creates a provider connection or sends messages.
AI suggestions / recorded-call lead conversion	Planned	Provider/model connection, consent and human review are required. No automatic claim that calls are recorded, transcribed or converted.
Background follow-up automation	Existing controls; scheduler verification required	In-app reminders exist. Runs while everyone is signed out require a healthy configured scheduler. Do not represent an unverified scheduler as always-on.
Saved report filters and scheduled reports	Planned	Core reports and filtering exist. Per-user saved views and scheduled delivery require a subsequent implementation and delivery testing.
Stalled deals and stage ageing	Planned	Reliable days-in-stage metrics should use stage history, with configurable thresholds and dashboard alerts. Do not infer stalled status from import time.
Advanced approval rules	Planned	Define actual discount, amount or stage exceptions first. No generic approval requirement is added to every normal sale.
Absence and reassignment	Existing bulk assignment; absence automation planned	Managers can use reviewed assignments. Automatic leave/exit handover and temporary replacement need explicit rules and audit testing.
Targets and KPIs	Existing	Sales targets, pipeline and analytics remain; distinguish calls, conversations, qualified opportunities, estimated pipeline and collected payments.
Backups, security and QA	Existing controls; ongoing operational checks	OTP, password history, audit, preview-write protection, QA screenshots and issue notes remain. Restore drills, provider delivery and scheduler health need periodic operational verification.
Enterprise tenancy / SSO / quotas	Planned	This release operates the existing DigiVista workspace. Separate company tenancy, SSO, pricing, usage metering and contractual quotas are not activated by selecting Enterprise.
Help and training	Included release guide + existing screen guides	Each new control includes plain-English purpose and expected result. Existing screen guides remain available; screenshots must be refreshed as screens evolve.

Acceptance checks before a company rollout

Test with Admin, salesperson, caller, provider and QA identities. Check direct API denial as well as hidden menus; filtered downloads must match visible filters. Package changes must preserve records, attribution and existing permission ceilings. Test mail delivery and scheduler health separately from screen rendering. Use dummy data for write tests.

No new provider subscriptions, live campaigns, company workspaces or staff privilege grants are performed by this release.