SaaS Mode

Agency Wallet & Transactions Detailed Transaction Report (ADTR).
To reconcile the Lead Connector costs to the Agency to what is being rebilled (set by the Rebilling Settings Category Multipliers) to the sub-accounts, today it takes two reports and tons of data fixing because of bugs and inconsistencies in the reporting. Setting the bugs and inconsistencies aside (see below), adding a few more columns to the ADTR relating to the Sub-account Detailed Transaction Report (SDTR) would be a quick fix, so just the ADTR could be used. Sub-Account Data – Must have fields from the SDTR: 1. Amount 2. Rebill Settings Category (currently, it’s loosely in the description. It is needed by itself) Example data: a. Phone System Resell Settings b. LC - Premium Triggers & Actions c. LC Email Verification d. Funnel AI e. Etc. 3. Rebill Settings Category Multiplier - adding Amount in the report, we could calculate this value by “amount/originalAmount”, but having the actual multiplier used in the transaction would be preferred. Nice to have, but not needed to reconcile the data - it would be a complete combination of the ADTR and the SDTR: Sub-Account Data: • walletCredits • totalBalance • balance • creditsUsed • discountAmount Bugs and Inconsistencies 1. The “originalAmount” column has positive and negative numbers. They should all be negative. 2. Every transaction needs a ref: {ID} in the description. The “description” column is a key to the corresponding re-billing transaction in the SDRT. It uses ref: {ID} to create a unique key. However, many transactions are missing the ref: {ID}.
4
·
Enhancement
Granular Permissions for View-Only Access at Agency Level
We’re requesting a feature that lets our admin and support teams view client accounts without having the ability to make changes. This will help them understand how clients are using our system and provide more proactive support while keeping account security intact. The goal is to enable certain team members to see important information in client accounts—like contact lists, workflows, message status, and integrations—without the risk of altering any settings or data. This visibility would allow our support team to catch issues early, such as incomplete SMS setups, and guide clients through solutions to improve their experience and retention. To make this effective, agency owners would need a simple way to assign view-only access to specific team members. By limiting access for non-technical staff, we can avoid accidental changes while still giving the team the insights they need to assist clients effectively. We recently faced an issue where an admin unintentionally made changes, which highlights the importance of view-only permissions. This feature would improve client support and reduce risk, allowing our team to handle accounts more securely and efficiently. Also if this granular permission allows us to remove certain parts of the software from agency users, such as them not being able to see contact data, or even workflows, pipeline, etc. Right Now we can enable "View & Manage" or disable it. I would like to be able to enable "View" only.
0
·
Enhancement
Load More
→