Wolk-us Support

When something breaks,
you know what to do.

It’s all here: where to report, how your case is classified, how fast we respond and what we need from you to fix it quickly. No guessing and no chasing anyone.

Wolk-us support specialist with a headset, ready to help
Wolk-us support desk

Official channels

A case is only covered by the SLA if it comes in through one of these channels. Messages sent any other way (personal chats, social media) don’t create a ticket or start the clock.

WhatsApp and phone

Fast entry with a chatbot and phone support. This is the channel for urgent issues and for finding out where to go next.

+1 (770) 525-1242

Support email

The formal channel: you can attach evidence, logs and screenshots, and it leaves a written record of the whole case.

support@wolk-us.com

Knowledge base

Documentation, tutorials and guides by module. Many cases get solved here without opening a ticket.

wolkvox.helpjuice.com

Your consoles

Before you report, check the status in Manager and Agent: campaigns, skills, permissions and active users.

See all access links

The SLA clock starts when we receive the case through an official channel and with enough minimum information. If critical evidence is missing, the case goes to Pending client and the clock pauses until it’s complete.

Before you report,
these seven things.

It’s not red tape: a case that arrives with this sorted out gets diagnosed in hours instead of days. Most of the time lost in support goes into asking for information that already existed.

0 of 7 · Start with the affected module

  1. Open the knowledge base

    It opens in a new tab. Your progress here is saved.

Incident, request or question?

Check the signals that apply to your case. The classification changes the response time, so it’s worth getting right.

Incident signals

Request signals

Question signals

Check at least one signal and we’ll tell you how to classify it.

Incident
priority levels.

Priority is assigned based on the real impact on your operation: number of users, how critical the process is, effect on production and whether a workaround exists. Not on how the person reporting it sees it.

1

The Service Desk logs and weighs the case.

2

The priority level is shared with you when the case is created.

3

The matrix sets the maximum times for resolution and escalation.

4

Critical cases can escalate to level 3 if they need specialized support.

Incident priority matrix: maximum resolution and escalation times
Incident type When it applies Max. resolution time Escalation time
Urgent Production stopped. Essential service down, many users affected, unable to operate. 2 h 1 h
High Critical, degraded. Key function affected with high impact, but with partial operation or a temporary workaround. 4 h 2 h
Medium Partial impact. Intermittent failure, limited segment, non-critical module or a viable workaround. 24 h 12 h
Low Non-blocking. Minor impact, a related operational question or an issue with no immediate impact. 48 h 24 h

Specialized escalation

Escalation to level 3
Level When it applies Max. resolution time Escalation time
Level 3 escalation Requires engineering, software, infrastructure, the manufacturer or a specialized vendor. 120 h 60 h

This matrix is the service baseline. For each client, what was agreed in the contract, the service order or the current SLA addendum takes precedence. If your agreement has different times, yours applies.

Platform limits.

A quick reference to rule out that your case is actually a known limit. It doesn’t replace the official technical documentation — if your case hits one of these numbers, let’s talk capacity, not failure.

Wolkvox Agent and Manager
  • Call concurrency per container: between 400 and 600 simultaneous calls, depending on traffic and server.
  • Concurrent agents per server: between 400 and 600, depending on enabled services.
  • Outbound predictive dialing: up to 15 concurrent calls per agent with Wolkvox telephony, 12 with your own telephony.
  • Simultaneous chats per agent: technical capacity up to 101, but the operational recommendation is 5.
  • Each chat session can stay active for up to 23 hours.
  • 1,000 tokens per Contact Center Master license per day; each token allows 2 simultaneous uses.
  • IPs per module: (call licenses + PBX licenses) × 10. Permanent IPs per module: 10.
  • Don’t use accents, “ñ” or special characters when naming configuration objects.
  • Campaign CSV: maximum 20 MB. Upload through Manager: 5,000 records per batch; through the API: 10,000.
  • Download through the API: up to 60,000 records or 400 MB.
  • Agent desktop updates starting on the 10th of each month; Agent web, on the day of the server deployment.
  • Manager updates on the 10th, 20th and 30th in server blocks.
Voice, IVR, campaigns and recordings
  • AMD analyzes the first 3 seconds to decide whether it’s a human or a machine: a long greeting may be classified as an answering machine.
  • When there’s silence, the system waits up to 15 seconds before classifying the call.
  • Campaign records per license: up to 7,000 on a shared server, 9,500 on a dedicated one.
  • Per server: 1,000 IVRs, 1,000 routing points, 3,000 extensions.
  • Screen recording only happens on calls longer than 15 seconds.
  • Manual bulk audio downloads are recommended between 8:00 p.m. and 8:00 a.m.
  • A campaign runs as predictive with 6 or more agents in the skill; with fewer, as progressive.
CRM
  • Storage: 2 GB per billed license.
  • Purge of records from retired operations: 6 months.
  • Time between API execution tasks: 40 seconds.
  • Maximum 350 fields per form.
  • Direct download: up to 35,000 records. In the background: up to 1,000,000.
  • Bulk upload: up to 50,000 records, files up to 80 MB, capped at 1,000,000 rows and 300 columns.
  • Web multi-session: 3 simultaneous sessions per active license. Inactivity logout: 8 hours.
  • API: up to 15,000 records per page; 2 simultaneous requests per token.
Omnichannel and interactions
  • Interaction queuing: 96 hours; after that, assignment may require a request.
  • Template: maximum 1,024 characters.
  • Deactivated connector: automatically purged after 30 days.
  • Chat: minimum 10 minutes to close, maximum 23 hours unless configured otherwise.
  • Export: up to 5,000 interactions for Instagram, Facebook and email.
  • Template sync: limit of 500.
  • Chatbot inactivity: 2 hours by default, configurable up to 23.
  • Inactivity messages: up to 3 quick-reply buttons; if there’s a URL, only 1 redirect button.

Report template.

Copy this, fill in the fields and send it through the channel you prefer. A case with this structure goes straight to diagnosis.

Case report
Subject: [Priority] [Client] - [Module] - [Short summary]

Case type: [Incident / Request / Question]
Proposed priority: [Urgent / High / Medium / Low]
Affected module: [Agent / Manager / CRM / Omnichannel / Voice / IVR / Campaigns / API / Reports]

Event start: [date, time and time zone]
Impact: [affected users, agents, campaigns, channels, processes]

Description: [what is happening]
Expected result: [what should happen]
Actual result: [what happens today]

Checks performed:
- Reproduction: [steps and result]
- Network / IP / VPN / firewall: [result]
- Computer, browser and version: [result]
- Permissions and credentials: [result]
- Knowledge base checked: [yes/no, article]
- Platform limits reviewed: [yes/no, which one]
- Recent internal changes: [yes/no, which one]

Evidence: [links, attachments, IDs, call or interaction number]
Contact: [name, role, phone, email]

Is it urgent and you need to talk to someone now?

Write to us on WhatsApp and we’ll continue by phone. For everything else, email leaves a better record.