> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/general-docs/features-road-map.md).

# Features Road Map

### Upcoming Features Road Map

<table><thead><tr><th width="587">Features</th><th>Release Date</th></tr></thead><tbody><tr><td>Auto Assign (Beta)<br>-All incoming chats will automatically assign &#x26; route to available agents</td><td>Already released</td></tr><tr><td>Auto Close<br>-If customer didn't reply to chat for specific time, the conversation will automatically closed and save as auto resolved.</td><td>30-Nov-2024</td></tr><tr><td>Multi Level SLA Setting<br>-Admin can setup SLA Configuration based on First Response Time, Resolution Time etc</td><td>Already released</td></tr><tr><td>WhatsApp for Business API</td><td>Already released</td></tr><tr><td>Telegram Channel</td><td>Already released</td></tr><tr><td>Instagram Comments<br>-Agents can reply Instagram Comments</td><td>Q1 2025</td></tr><tr><td>Outbound Broadcast Campaigns<br>-Send Bulk Outbound Message to customer preferred channels at scale</td><td>Q2 2025</td></tr><tr><td>TikTok Shop Channel<br>-Agents can reply TikTok Shop Message </td><td>Q1 2025</td></tr><tr><td>Call Transcript<br>-Auto summarize Call Transcript from Call Recording Data with AI</td><td>Q1 2025</td></tr><tr><td>Chat Transcript<br>-Auto summarize Chat Transcript from Call Recording Data with AI</td><td>Q1 2025</td></tr><tr><td>Auto Sentiment Scoring<br>-Automatically score customer sentiment</td><td>Q1 2025</td></tr><tr><td>Auto Topic Detection<br>-Detect main topics in customer communications</td><td>Q1 2025</td></tr><tr><td>WeChat Business Channel<br>-Integrate WeChat as a business communication channel</td><td>Q2 2025</td></tr><tr><td>Twitter (X) Channel<br>-Enable customer support and engagement via Twitter</td><td>Q3 2025</td></tr><tr><td>CRM Integration Marketplace<br>-Expand CRM integrations to facilitate better data syncing and automation</td><td>Q3 2025</td></tr><tr><td>Outbound Automation Call Campaign<br>-Automate outbound calling campaigns to improve reach and efficiency</td><td>Q4 2025</td></tr><tr><td>Automatic Translation <br>-Translate communications automatically in multiple languages</td><td>Q1 2026</td></tr><tr><td>Automatic QA Scoring<br>-Automatically score quality of agent responses</td><td>Q2 2026</td></tr><tr><td>Outbound AI Agent<br>-Deploy AI agents for outbound customer interactions</td><td>Q3 2026</td></tr><tr><td>Advanced Behavioral Analytics<br>-Analyze customer behavior in-depth to tailor support and marketing strategies effectively.</td><td>Q1 2027</td></tr><tr><td></td><td></td></tr></tbody></table>

if you have features suggestion or ideas, please send us email at <support@klink.cloud>

{% hint style="info" %}
Want to try our upcoming features, just let us know. We will add give you early access
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.klink.cloud/general-docs/features-road-map.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.