Organization Profile
Configure organization-wide settings that apply to all agents and users in your Convrs account.
Organization Settings allow administrators to customize how Convrs operates for their organization, including office hours, agent behavior, security policies, and third-party integrations.
General Settings
Configure basic organization information and outbound chat requirements.
Update Organization Name and Logo
Change your organization's display name and upload a custom logo.
Steps:
- Navigate to Administration > Organization Settings.
- Click the General tab.
- Enter your organization name in the Organization Name field.
- Click the Upload new Logo button to select an image file.
- Click Save changes.
- Allowed image formats are JPG, GIF, or PNG
- Maximum file size is 1500KB
Configure Outbound Chat Requirements
Set mandatory fields for agents when starting new outbound conversations.
Steps:
- Navigate to Administration > Organization Settings.
- Click the General tab.
- Enable Make it mandatory for new outbound chats to have an email and name entered to require contact information.
- Enable Make it mandatory for new outbound chats to come from external CRM to restrict outbound chats to CRM-linked contacts only.
- Click Save changes.
| Field | Description |
|---|---|
| Require email and name | When enabled, agents must enter an email address and name before starting an outbound chat |
| Require CRM link | When enabled, outbound chats can only be initiated from contacts linked to an external CRM system |
Office Hours
Define your typical business hours and configure automated responses for when your team is unavailable.
Set Office Working Hours
Configure the times and days when your office is open for live agent support.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Office Hours tab.
- Set the Office Open Time (e.g., 09:00:00).
- Set the Office Close Time (e.g., 17:00:00).
- Select your Office Time Zone from the dropdown.
- Check the days of the week when your office is open.
- Click Save changes.
Result: When agents are offline and users contact you outside office hours, they will receive the "Out of hours" message configured in your chatbot flow.
| Field | Description |
|---|---|
| Office Open Time | The time your office typically opens (24-hour format) |
| Office Close Time | The time your office typically closes (24-hour format) |
| Office Time Zone | The timezone your office operates in |
| Days of the week | Select which days your office is open (Monday through Sunday) |
Configure Missed Chat Notifications
Set up email notifications when chats are missed by agents.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Office Hours tab.
- Enable Send an email report when a chat is missed.
- Enter the email address in the Email Address field.
- Click Save changes.
Result: When a chat is missed, an email report containing user details and the chat transcript will be sent to the specified address.
Agent Chat Handling Options
Configure how chats are allocated and managed for agents in your organization.
Set Maximum Chats Per Agent
Limit the number of concurrent chats that can be assigned to each agent.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Agent Chat Handling Options tab.
- Enter a value in the Maximum number of chats field (1-9).
- Click Save changes.
Result: When an agent reaches their maximum chat limit, their status is automatically set to busy and new incoming chats will not be allocated to them.
Configure Offline Queue Behavior
Control what happens when a user responds to a chat while their assigned agent is offline.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Agent Chat Handling Options tab.
- Enable or disable Move active chat to queue if a user responds when an agent is offline.
- Click Save changes.
Result: When enabled, the system will first try to allocate the message to other available agents. If none are available, the user is placed in the queue.
Configure Automatic Chat Closure
Set up automatic closure of inactive chats and handling of chats when agents don't log in.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Agent Chat Handling Options tab.
- Set the number of days in Automatically close a chat due to inactivity (0-60 days).
- Set the number of days in Move an allocated chat to the queue if the agent hasn't logged in (0-60 days).
- Click Save changes.
| Field | Description |
|---|---|
| Close after inactivity | Number of days of inactivity (from both user and agent) before a chat is automatically closed. Set to 0 to never auto-close. |
| Move to queue after no login | If an agent hasn't logged in for this many days and a user sends a message, the chat is closed and the user is placed in the queue. Set to 0 to keep chats with the agent. |
Password Policy
Enforce password requirements to improve security for your organization's agent accounts.
Configure Password Requirements
Set up password complexity rules and expiration policies for your organization.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Password Policy tab.
- Enable Enforce a password policy for your Organization.
- Set the Minimum number of characters (1-30).
- Set the Maximum number of characters (1-30).
- Set the Minimum number of mixed case characters (0-10).
- Set the Minimum number of digits (0-10).
- Set the Number of special characters (0-10).
- Set Force a password change after a certain number of days (1-180).
- Optionally enable Passwords cannot be reused.
- Click Save changes.
| Field | Description |
|---|---|
| Minimum characters | Minimum password length required |
| Maximum characters | Maximum password length allowed (hard limit of 30) |
| Mixed case characters | Minimum number of uppercase and lowercase letters required |
| Digits | Minimum number of numeric characters (0-9) required |
| Special characters | Minimum number of special characters (e.g., !"#$%&) required |
| Password expiry | Number of days after which users must change their password |
| No password reuse | Prevents users from reusing previously used passwords |
Single Sign-On (SSO)
Enable Single Sign-On to allow agents to log in using your organization's identity provider.
Enable Single Sign-On
Configure SSO with your preferred identity provider (Google, Microsoft, Okta, or Generic SAML).
Steps:
- Navigate to Administration > Organization Settings.
- Click the Single Sign-On (SSO) tab.
- Enable Enable SSO.
- Select your SSO provider from the Your SSO Provider dropdown.
- If using Generic SAML, complete the additional SAML configuration (see below).
- Optionally enable Enable Agents to login with username and password as well as with SSO for dual authentication support.
- Click Save changes.
Result: Agents will be able to log in using your organization's identity provider credentials.
| Provider | Description |
|---|---|
| Sign in with Google Workspace accounts | |
| Microsoft | Sign in with Microsoft 365/Azure AD accounts |
| Okta | Sign in with Okta identity management |
| Generic SAML | Sign in with any SAML 2.0 compatible identity provider |
- Enable dual login (username/password and SSO) during migration to make the transition smoother
- Test SSO with a single user before enabling for the entire organization
Configure Generic SAML
Set up SAML authentication with a custom identity provider.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Single Sign-On (SSO) tab.
- Enable Enable SSO and select Generic SAML.
- Copy the Assertion URL and Entity ID values and provide them to your SAML vendor.
- Enter the Single Sign on URL provided by your SAML vendor.
- Paste the Certificate provided by your SAML vendor.
- Optionally enable Use Role provided by SAML vendor if you want roles to be assigned from your identity provider.
- Click Save changes.
| Field | Description |
|---|---|
| Assertion URL | Convrs endpoint URL (read-only) - provide this to your SAML vendor |
| Entity ID | Convrs entity identifier (read-only) - provide this to your SAML vendor |
| Single Sign on URL | The SSO URL from your SAML vendor |
| Certificate | The X.509 certificate from your SAML vendor |
| Use Role from SAML | When enabled, user roles are assigned based on SAML assertions |
Third Party Data Processors
Enable or disable third-party services that process your organization's data to provide additional functionality.
Enable Message Translation
Allow automatic translation of messages between different languages.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Third Party Data Processors tab.
- Enable Message Translation.
- Click Save changes.
Result: Agents can use the auto-translate feature to communicate with users in different languages.
Enable AI Writing Assistant
Enable AI-powered spelling, grammar checking, and writing style suggestions for agents.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Third Party Data Processors tab.
- Enable AI Writing Assistant.
- Click Save changes.
Result: Agents can use AI to improve their message quality with spelling corrections, grammar fixes, and writing style guidance.
Enable AI Sentiment and Chat Summary
Enable AI-powered sentiment analysis and automatic summaries for closed chats.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Third Party Data Processors tab.
- Enable AI Sentiment and Chat Summary.
- Click Save changes.
Result: Closed chats will automatically receive sentiment scores and AI-generated summaries for easier review and reporting.
Reports
Configure the thresholds used to colour-code KPIs across your organization's reports.
Configure Report Thresholds (RAG)
Set Red, Amber, and Green thresholds that determine how KPI values are colour-coded in reports such as Executive Summary, Team Scorecard, Quality Assurance, Channel Performance, and Country Performance.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Reports tab.
- For each KPI, enter a Green threshold and an Amber threshold value.
- Click Save changes.
Result: Reports will use your custom thresholds to colour-code KPI values as green, amber, or red.
| KPI | Green Threshold (Default) | Amber Threshold (Default) | Direction |
|---|---|---|---|
| Average Wait Time | At or below 60 seconds | At or below 120 seconds | Lower is better |
| Average Response Time | At or below 45 seconds | At or below 90 seconds | Lower is better |
| CSAT Score | At or above 4.0 | At or above 3.5 | Higher is better (scale 1–5) |
| Sentiment | At or above 60% | At or above 40% | Higher is better |
| AI Bot Containment | At or above 70% | At or above 50% | Higher is better |
- For "lower is better" KPIs (wait time, response time), values at or below the green threshold are green; above green but at or below amber are amber; above amber are red
- For "higher is better" KPIs (CSAT, sentiment, containment), values at or above the green threshold are green; below green but at or above amber are amber; below amber are red
- Adjust thresholds to match your organization's service level agreements
Native Application
Control access to the Convrs mobile application for your organization.
Configure Native App Access
Control which agents can use the Convrs native mobile application.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Native Application tab.
- Select an option from the Who in your Organization can use the Native App? dropdown.
- Click Save changes.
| Option | Description |
|---|---|
| No one | Disable native app access for all agents |
| Everyone | Allow all agents to use the native app |
| Agents with the permission NativeApp | Only agents with the specific NativeApp permission can use the mobile app |
- Use permission-based access for fine-grained control over which agents can use mobile devices
- The native app is ideal for agents who need to respond to chats while away from their desk
Developer — WebChat Signing Secret
Configure a signing secret that allows your backend to create JSON Web Tokens (JWTs) for securely identifying logged-in users in the webchat widget. When a user visits your site, your backend signs a token containing user details (such as name, email, or user ID) with this secret. Convrs verifies the token when the webchat connects, linking the conversation to a known user identity.
For full details on JWT structure, supported claims, and backend integration examples, see Secure User Identity for Web Chat (JWT).
Generate a Signing Secret
Generate a new signing secret for your organization so your backend can create JWT tokens for webchat user identification.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Developer — WebChat tab.
- Click the Generate Secret button.
- A modal will appear displaying your new signing secret. Copy the secret and store it securely in your backend configuration.
- Click Close to dismiss the modal.
Result: Your organization now has an active signing secret. Your backend can use it to sign JWT tokens that identify users connecting via the webchat widget.
- Store the secret in a secure location such as an environment variable or secrets manager — never hard-code it in client-side code
- Only administrators should have access to this page
Rotate the Signing Secret
Replace the current signing secret with a new one while allowing existing integrations time to update.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Developer — WebChat tab.
- Click the Rotate Secret button on the current secret card.
- Confirm the rotation when prompted.
- A modal will appear displaying the new signing secret. Copy it and store it securely.
- Update your backend to use the new secret.
Result: A new signing secret is generated and the previous secret enters a 48-hour grace period. During this window, tokens signed with either secret will be accepted by Convrs.
- Plan secret rotations during low-traffic periods to minimise risk
- Use the 48-hour grace period to roll out backend updates gradually across environments
Revoke a Previous Secret
Immediately invalidate a previous signing secret that is still within its grace period.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Developer — WebChat tab.
- In the Previous Secret (Grace Period) card, click the Revoke Now button.
- Confirm the revocation when prompted.
Result: The previous secret is immediately invalidated. Only tokens signed with the current secret will be accepted.
Verify a JWT Token
Test whether a JWT token is valid by verifying it against your organization's signing secret.
Steps:
- Navigate to Administration > Organization Settings.
- Click the Developer — WebChat tab.
- Scroll to the Test a JWT Token section.
- Paste a JWT token into the text area.
- Click the Verify Token button.
Result: A success or failure message is displayed. If valid, the result shows which secret was used (current or previous) and the decoded token claims. If invalid, the error reason is displayed along with any partially decoded claims.
- Use this tool during integration setup to confirm your backend is generating tokens correctly
- After a secret rotation, verify a token signed with the new secret to confirm the update was successful
Integration Example
The tab includes a code snippet showing how to pass a signed JWT to the webchat widget on your website. Your backend generates the token server-side, and the page sets it in a ConvrsUser JavaScript variable before the widget loads. The webchat widget reads this variable on connection and sends the token to Convrs for verification.