VQConnector-VCC-1.5.3

Release Update:

- AHT calculation improvement:

Reason: AHT was changing very fast and it became 0 on zero calls or zero agents
Requirement: AHT value should be stable and should not become 0
Solution: AHT will include 1 hour of calls in its calculation which will make it stable and it will also retain its old value.
Ticket: https://trello.com/c/L8eoSoDE/84-improved-way-to-calculate-aht
Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--aht

VQConnector-VCC-1.5.2

Release Update:

- Connector Version Format Update:

Reason: needed the version number in new format
Requirement: Send version number in following format to virtualQ: "VCC - QConnect v[version]"
Solution: Connector Version will be now as following format: "VCC - QConnect v[version]"
Ticket: https://trello.com/c/5NYpbYYO/71-send-connector-version-to-virtualq
Docuementation: https://github.com/virtualq/QConnect-Release/wiki/Product-Version-Information#--from-virtualq-dashborad

VQConnector-VCC-1.5.1

Release Update:

- Connector Version Update:

Reason: need to display connector version on virtualQ dashborad
Requirement: Use VirtualQ API to send version number at the start of QConnect
Solution: Send Connector version to VirtualQ dashborad via VirtualQ C# SDK at the start of QConnect
Ticket: https://trello.com/c/5NYpbYYO/71-send-connector-version-to-virtualq
Docuementation: https://github.com/virtualq/QConnect-Release/wiki/Product-Version-Information#--from-virtualq-dashborad

VQConnector-VCC-1.5.0

Release Update:

- Direct SMS capability via Voxtron:

Reason: Clients want to send sms to customer via vcc system.
Requrement: QConnect should be able to lineup costumer on virtualQ which want sms notification via CallInExt and then should be able to inform vcc when its time to notify the customer. So sms goes via vcc and not virtualQ
Solution: QConnect can now lines up customer via CallInExt and informs vcc to send sms notification.
Ticket: https://trello.com/c/kkNmjDsU/70-as-qconnect-i-want-to-send-notification-sms-directly-from-voxtron-qconnect
Docuementation: https://github.com/virtualq/QConnect-Release/wiki/Features#--callinext-feature

- AHT Improvement:

Reason: QConnect AHT calculation for waiting fields was bit off.
Requirement: Needed better AHT on clients.
Solution: Added improvements to AHT calculations
Behavior: AHT will be more accurate now.
Ticket: https://trello.com/c/L8eoSoDE/84-improved-way-to-calculate-aht

- Configurable AgentServiceList Transmission

Reason: AgentServiceList was not needed for virtual stats
Requirement: Stop sending agentList of virtualQ
Solution: Make Transmission of agent list configurable so it can be turned on and off as per requirement.
Ticket: https://trello.com/c/BML4ypV9/89-make-agentlist-transmission-to-vq-configurable
Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--stop-serviceagentlist-transmission-to-virtualq

- Set EWT = 0 in DB

Reason: EWT was set 2 sec in DB as default.
Requirement: change EWT db default to 0.
Solution: changed EWT db default to 0.
Ticket: https://trello.com/c/wLxxMRnI/87-set-ewt-0-for-db-defaults

- ContactId column add in Calback table in db

Reason: deployments team needed to run queries on callback table by ContactId. That was not present in past builds
Requirement: Add ContactId column in callback table
Solution: ContactId colmun added in callback table
Ticket: https://trello.com/c/VVS9DCUC/85-callback-db-table-update
Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--callback-table-update

VQConnector-VCC-1.4.1

Release Update:

- Version Number Feature:

Reason: QConnect didn't show its latest version number.
Requirement: Needed version number to track QConnect changeset on clients.
Solution: Add support for version number
Behavior: QConnect will show version number now.

Documentation: visit the link to see where you can find QConnect version info: https://github.com/virtualq/QConnect-Release/wiki/Product-Version-Information

VQConnector-VCC-1.4.0

Release Update:

- Phone Number Hashing:

• Requirement:

  • When a caller is choosing to use virtualQ, the phone number is hashed and stored in QConnect (same place where phone number is stored).
  • When API request to virtualQ is made, the Hash is supplied, instead of the phone number
  • When QConnect is checking virtualQ for callers, we always compare the hash we receive with the ones we have stored, so we know what caller it is.

• Behavior:
  This feature allows QConnect to sends virtualQ hashes of phone numbers instead of actual phone numbers. This is done due for the data protection of call center customers.

  • It will only work for normal calls with source = "Phone" or "Mobile"
  • Its using MD5 encryption algorithm.
  • Its configurable, means it can be enable or disabled as per need. Configuration "EnablePhoneNumberHashing" can be changed from database.
  • Phone numbers and their hashes are stored in database table "PhoneNumberHashes".

• Fix: Added support for Phone Number hashing feature in QConnect.

Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--hash-phone-number

VQConnector-VCC-1.3.0

Release Update:

- AHT

Reason: AHT was not working on QConnect
Fix: Added AHT feature support in QConnect
Documentation: https://github.com/virtualq/QConnect-Release/wiki/Features#--aht

- Ewt Min value:

Reason: Ewt min value was 120ms
Fix: changed it to 0
it can also be changed from db configurations, see following link: https://github.com/virtualq/QConnect-Release/wiki/Features#--ewt

- Ewt service change

Reason: EWT of waiting field was calculating very high due to appointments callbacks.
Solution: Removed appointments from EWT calculation of a queue.
Behavior: EWT will be normal now.
Docuementation: https://github.com/virtualq/QConnect-Release/wiki/Features#--ewt

- API as call source

Solution: Added support for Api as a call source
Behavior: now QConnect will work similar for API call source as it does for widget.

VQConnector-VCC-1.2.0

Release Updates

- Ewt service change

Reason: EWT of waiting field was calculating very high due to appointments callbacks.
Solution: Removed appointments from EWT calculation of a queue.
Behavior: EWT will be normal now.

- API as call source

Solution: Added support for Api as a call source
Behavior: now QConnect will work similar for API call source as it does for widget.

VQConnector-VCC-1.1.2

Feature Updates

- Contact Id assignment to appointment:

Issue: contact id was not assigning to appointment call correctly.
Solution: assigned contact id to appointment.
Behavior: now for each appointment there will be a unique contact id and so will a unique BO on vcc side.

VQConnector-VCC-1.1.1

Feature Updates:

- Make Appointment:

Reason: appointment feature was not supported in QConnect
Solution:
- Added appointment as new call source
- Added support for appointment feature in QConnect
Behavior: QConnect will be able to handle appointments as well.
Note: This is not a major update so only increasing minor version.