Patch 6.7.5
TLDialer
- DEAD CALLS ARE BACK!
- You should now be able to tell when a client has hung up.
- This plays nicely with Transfers as well. If an agent hangs up the transfer, the person transferred in will be considered a Dead Call and should hang up and then dispo.
- If the client hangs up during a transfer, only the person who took the call will see it dead as they are still connected to the transferred person.
- Transfer Count
- The Icon for the Transfer Menu will now update with how many people you are in a conference with! Wild! More to come with this!
- Call Menus added to Search. Queryable and works with Column Builder
- Should make it easier to check out what is configured.`
- DID added to Search. Queryable and works with Column Builder
- Should make it easier to check out what is configured.
- Removed 2 Queries from the TLDialer Processor, now should be a little faster. Also added a couple joins related to Transfers, which made slightly slower. All in all, no performance difference.
Sockets
- TLD itself now has the ability to push data to the sockets system to update leads and policies, and notify the user that this has occured, aside from another user.
Merge Leads
The long awaited Feature is almost here! You can now merge two or more leads together. The interface is pretty straight forward!
This is currently in testing. It works! But we want to be sure it is a smooth process.
- Check off boxes for leads you want to merge
- Press Merge Leads
- Choose Lead you want to merge INTO.
- Select Fields you want to Keep / Protect from that lead.
- For each Lead being Merged In, select the fields you want to merge in, (There is a check all button).
- Drag and Drop the Leads in the order you want them to merge from first to last.
- Example, if You are merging 2 (3 Selected) leads into lead 1, and lead 1 has no first name, but Lead 2 and Lead 3 have two different first names, it will accept Lead 2’s First Name, then afterwards overwrite that with Lead 3’s First Name.
- If you need to merge a different field, you can always Remerge a merged lead, as the lead data is the only thing left on the record besides a note in the action log as to where the lead was merged to (which will not be remerged)
- Example, if You are merging 2 (3 Selected) leads into lead 1, and lead 1 has no first name, but Lead 2 and Lead 3 have two different first names, it will accept Lead 2’s First Name, then afterwards overwrite that with Lead 3’s First Name.
Notes
- Notes now have an Account ID associated with them for later search features
Dependents
- Dependents now have an Account ID associated with them for later search features
Favorites
- Favorites now have an Account ID associated with them for later search features
Callbacks
- Callbacks now have an Account ID associated with them for later search features
Survey Answers
- Survey Answers now have an Account ID associated with them for later search features
Survey Questions
- Survey Questions now have an Account ID associated with them for later search features
Lead Relational
- Lead Relational now has an Account ID associated with them for later search features
Contacts
- Fixed Dependent, Policy and Note Grab Tabs. They should all work now. Some minor CSS and JS issues prevented them from all working consistently.
- When a contact is in “Merged” status, the lead can no longer be modified or saved.
- Fixed a CSS Issue with Subsidized Premiums on Smaller Screens.
Policy Statuses
- Added Pending: Documentation. It can be disabled.
General
- Date Quarters logic fixed up.
- Fixed an issue with Indexes related to Touchpoint Queries.
- More system optimizations, less memory usage, less time processing.
- Refactored some old internals.
- Removed unused code.
- Refactored Menu and Filter Open / Close code. Makes more sense now.