Mission Labs Limited

SmartAgent Automate - Chatbot

SmartAgent Automate will transform your customer care and sales teams with multi-channel and multilingual, asynchronous chat which seamlessly switches between integrated bot and agent, depending on the context. Completely deflect high volume, low value contacts via our automated chatbot, leaving your agents free to focus on serving high value contacts.

Features

  • Instant live chat capability
  • Customisable and configurable chat window and flows
  • Conversational UX journeys
  • Natural Language Processing (NLP) to understand intent
  • Real-time translation of conversations in over 50 languages
  • Social media support (Facebook Messenger, WhatsApp, Twitter DMs)
  • Integrations into existing systems
  • Seamless hand-off from bot to agent (and back again)
  • AI / ML driven insights (e.g. sentiment analysis)
  • Clear commercials with a UK supplier

Benefits

  • Reduced contact
  • Available 24/7, 365 days per year
  • Faster customer service and increased sales
  • Lower Average Handle Time and improved First Contact Resolution
  • Personalised customer experiences
  • Light touch implementation
  • Maximise human skills and time for high value contact
  • Future proofed solution and roadmap ownership
  • Enable multi-channel customer journey
  • Reliable, highly available, fault tolerant and scalable

Pricing

£0.10 to £0.50 per transaction

Service documents

Framework

G-Cloud 11

Service ID

1 8 6 6 6 9 6 1 4 9 7 9 2 3 9

Contact

Mission Labs Limited

Commercial Team

03330505050

info@missionlabs.co.uk

Service scope

Software add-on or extension
Yes, but can also be used as a standalone service
What software services is the service an extension to
• Web and mobile
• Social
• CRM
• ERP
• Case Management
• WFM systems
• eCommerce systems
• Back-office systems
• Propriety applications
• Microsoft Bot Framework
• Microsoft Azure Bot Service/LUIS
• Amazon Lex
• Amazon AI/ML
• IBM Watson
• Google Cloud AI
• Google Dialogflow
Cloud deployment model
Public cloud
Service constraints
N/A
System requirements
N/A

User support

Email or online ticketing support
Email or online ticketing
Support response times
We aim to respond as quickly as possible, typically within 60 mins for normal queries. This is operated Monday-Friday unless otherwise agreed.
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
None or don’t know
Phone support
Yes
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
No
Onsite support
Yes, at extra cost
Support levels
Support is provided based on standard P1, P2, P3, P4 classifications. Support channels provided include phone and email. Service Level Agreements (SLA) will be agreed with the customer as part of the planning and migration stages. Costs for this will be determined at this stage.
Support available to third parties
No

Onboarding and offboarding

Getting started
We will provide all onboarding and training required to operate our services.

In addition, we can provide full documentation, videos and how-to guides, online and in-person training.
Service documentation
Yes
Documentation formats
  • HTML
  • PDF
End-of-contract data extraction
We will be able to export data required from the service.
End-of-contract process
This varies based on the contract. Services can be decommissioned and terminated as part of the agreement.
There may be costs associated with this process subject to the pre-agreed exit provisions.

Using the service

Web browser interface
Yes
Supported browsers
  • Internet Explorer 10
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
Application to install
No
Designed for use on mobile devices
No
Service interface
No
API
No
Customisation available
Yes
Description of customisation
Conversational flows, chat window, contact routing options and rules, application access and reporting rights, third party integrations, custom logic.
Overall our solution can be fully customised to meet any business needs and goals.

Scaling

Independence of resources
We provide a very scalable environment for your solution with continuous monitoring in place.

Analytics

Service usage metrics
Yes
Metrics types
Reporting can be provided as required. For example:

- contacts taken
- hold times
- contact queues
- agent performance

On top of this we can provide any form of custom reporting within SmartAgent.
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request

Resellers

Supplier type
Reseller providing extra features and support
Organisation whose services are being resold
Amazon Connect, Google Contact Centre, Genesys, Mitel, Cisco, Avaya, 8x8

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
  • United Kingdom
  • EU-US Privacy Shield agreement locations
User control over data storage and processing locations
Yes
Datacentre security standards
Supplier-defined controls
Penetration testing frequency
At least every 6 months
Penetration testing approach
Another external penetration testing organisation
Protecting data at rest
Other
Other data at rest protection approach
We provide a secure environment for your solution and we adhere to best practice in terms of privacy, data protection, security protections and control processes.
Data sanitisation process
Yes
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach
In-house destruction process

Data importing and exporting

Data export approach
We can also allow you to export data into systems of your choice such as part of the project planning phase if you wish.

Data can be stored as required with a number of export mechanisms.
Data export formats
  • CSV
  • ODF
  • Other
Other data export formats
UTF-8 encoded JSON document
Data import formats
  • CSV
  • ODF
  • Other
Other data import formats
UTF-8 encoded JSON document

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection between networks
Network devices, including firewall and other boundary devices, are in place to monitor and control communications at the external boundary of the network and at key internal boundaries within the network. These boundary devices employ rule sets, access control lists (ACL), and configurations to enforce the flow of information to specific information system services.

ACLs, or traffic flow policies, are established on each managed interface, which manage and enforce the flow of traffic. ACL policies are approved by Amazon Information Security.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection within supplier network
Customer environments are logically segregated to prevent users and customers from accessing resources not assigned to them. AWS gives customers ownership and control over their content by design through simple, but powerful tools that allow customers to determine how their content will be secured in transit.
AWS enables customers to open a secure, encrypted channel to AWS services using TLS/SSL, and/or IPsec or TLS VPN (if applicable), or other means of protection the customer wish to use.
API calls can be encrypted with TLS/SSL to maintain confidentiality; the AWS Console connection is encrypted with TLS.

Availability and resilience

Guaranteed availability
Our core SmartAgent solution resides on AWS (see below their SLAs) we also provide customer specific SLAs subject to requirements.

AWS currently provides SLAs for several services. Due to the rapidly evolving nature of AWS’s product offerings, SLAs are best reviewed directly on our website via the links below:

• Amazon EC2 SLA: http://aws.amazon.com/ec2-sla/
• Amazon S3 SLA: http://aws.amazon.com/s3-sla
• Amazon CloudFront SLA: http://aws.amazon.com/cloudfront/sla/
• Amazon Route 53 SLA: http://aws.amazon.com/route53/sla/
• Amazon RDS SLA: http://aws.amazon.com/rds-sla/
• AWS Shield Advanced SLA: https://aws.amazon.com/shield/sla/

Well-architected solutions on AWS that leverage AWS Service SLA’s and unique AWS capabilities such as multiple Availability Zones, can ease the burden of achieving specific SLA requirements.
Approach to resilience
The AWS Business Continuity plan details the process that AWS follows in the case of an outage, from detection to deactivation. AWS has developed a three-phased approach: Activation and Notification Phase, Recovery Phase, and Reconstitution Phase. This approach ensures that AWS performs system recovery and reconstitution efforts in a methodical sequence, maximizing the effectiveness of the recovery and reconstitution efforts and minimizing system outage time due to errors and omissions.

AWS maintains a ubiquitous security control environment across all regions. Each data centre is built to physical, environmental, and security standards in an active-active configuration, employing an n+1 redundancy model, ensuring system availability in the event of component failure. Components (N) have at least one independent backup component. All data centres are online and serving traffic. In case of failure, there is sufficient capacity to enable traffic to be load-balanced to the remaining sites.

Customers are responsible for implementing contingency planning, training and testing for their systems hosted on AWS. AWS provides customers with the capability to implement a robust continuity plan, including the utilization of frequent server instance back-ups, data redundancy replication, and the flexibility to place instances and store data within multiple geographic regions across multiple Availability Zones.
Outage reporting
Public dashboard; personalised dashboard with API and events; configurable alerting (email / SMS / messaging)

Identity and authentication

User authentication needed
Yes
User authentication
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
  • Other
Other user authentication
AWS controls access via unique user ID/password authentication. No actions are permissible without authentication. Remote access is multi-factor, login attempts are limited, remote administrative access attempts are logged and reviewed by Security. Suspicious activity initiates incident response procedures.

A session lock out policy that is systematically enforced: locks are retained until identification/authentication procedures are concluded.

AWS’s Identity and Access Management (IAM) system controls access to AWS services/resources. IAM facilitates the issuance of access permissions per user/group. MFA is available at no extra cost.

Other supported user authentication protocols include: - single sign on - OAuth 2.0 - SAML
Access restrictions in management interfaces and support channels
IAM provides user access control to AWS services, APIs and specific resources. Other controls include time, originating IP address, SSL use, and whether users authenticated via MFA devices.

API calls can be encrypted with TLS/SSL for confidentiality and customers can use TLS/SSL-protected API endpoints.
API calls can be encrypted with TLS/SSL for confidentiality and customers can use TLS/SSL-protected API endpoints.
Access restriction testing frequency
At least every 6 months
Management access authentication
2-factor authentication

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
User-defined
Access to supplier activity audit information
You control when users can access audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
No
ISO 28000:2007 certification
No
CSA STAR certification
No
PCI certification
No
Other security certifications
No

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • ISO/IEC 27001
  • Other
Other security governance standards
Cyber Essentials Plus; ISO 27017; ISO 27018; SOC 1/2/3

Cloud security at AWS is the highest priority. As an AWS customer, you will benefit from a data centre and network architecture built to meet the requirements of the most security-sensitive organizations.
Information security policies and processes
AWS implements formal, documented policies and procedures that provide guidance for operations and information security within the organisation. Policies address purpose, scope, roles, responsibilities and management commitment.

Employees maintain policies in a centralised and accessible location. AWS Security Assurance is responsible for familiarizing employees with the AWS security policies.

AWS has established information security functions that are aligned with defined structure, reporting lines, and responsibilities. Leadership involvement provides clear direction and visible support for security initiatives.

The output of AWS Leadership reviews include any decisions or actions related to:

• Improvement of the effectiveness of the ISMS.
• Update of the risk assessment and treatment plan.
• Modification of procedures and controls that affect information security to respond to internal or external events that may impact the ISMS.
• Resource needs.
• Improvement in how the effectiveness of controls is measured.

Policies are approved by AWS leadership at least annually or following a significant change to the AWS environment.

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
Changes to AWS services and features follow secure software development practices, including security risk reviews prior to launch. Developer access to production environments is via explicit access system requests, subject to owner review and authorisation.

Teams set bespoke change management standards per service, underpinned by standard AWS guidelines.

All production environment changes are reviewed, tested and approved. Stages include design, documentation, implementation (including rollback procedures), testing (non-production environment), peer to peer review (business impact/technical rigour/code), final approval by authorised party.

Emergency changes follow AWS incident response procedures. Exceptions to change management processes are documented and escalated to AWS management.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
AWS Security performs vulnerability scans on the host operating system, web applications, and databases in the AWS environment. Approved 3rd party vendors conduct external assessments (minimum frequency: quarterly). Identified vulnerabilities are monitored and evaluated. Countermeasures are designed and implemented to neutralise known/newly identified vulnerabilities.

AWS Security monitors newsfeeds/vendor sites for patches and receives customer intelligence via http://aws.amazon.com/security/vulnerability-reporting/.

AWS customers are responsible for all scanning, penetration testing, file integrity monitoring and intrusion detection for their Amazon EC2 and Amazon ECS instances/ applications. Scans should include customer IP addresses (not AWS endpoints). AWS endpoint testing is part of AWS compliance vulnerability scans.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
AWS deploys (pan-environmental) monitoring devices to collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth-usage. Devices monitor:

• Port scanning attacks
• Usage (CPU, processes, disk utilization, swap rates, software-error generated losses)
• Application metrics
• Unauthorized connection attempts

Near real-time alerts flag potential compromise incidents, based on AWS Service/Security Team- set-thresholds.

Requests to AWS KMS are logged/ visible via the account’s AWS CloudTrail Amazon S3 bucket. Logs provide request information, under which CMK, and identify AWS resources protected through the CMK use. Log events are visible to the customer after turning on AWS CloudTrail in their account.
Incident management type
Supplier-defined controls
Incident management approach
AWS adopts a three-phased approach to manage incidents:

1. Activation and Notification Phase
2. Recovery Phase
3. Reconstitution Phase

To ensure the effectiveness of the AWS Incident Management plan, AWS conducts incident response testing, providing excellent coverage for the discovery of defects and failure modes as well as testing the systems for potential customer impact.

The Incident Response Test Plan is executed annually, in conjunction with the Incident Response plan. It includes multiple scenarios, potential vectors of attack, the inclusion of the systems integrator in reporting and coordination and varying reporting/detection avenues.

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)

Public sector networks

Connection to public sector networks
No

Pricing

Price
£0.10 to £0.50 per transaction
Discount for educational organisations
No
Free trial available
No

Service documents

Return to top ↑