Feature Request - HaloAgents

The best ideas in HaloAgents come from teams using it every day. If you wish HaloAgents did something it doesn’t, tell us. We read every request and they directly shape the roadmap.

Where to send it

In-App Chat

Open the dashboard, click Contact Support, and start with Feature request: in the first message. The fastest way and we can ask follow-ups in real time.

Email

Email support@haloagents.ai with Feature Request in the subject. Good for longer write-ups or when you want to share a doc.

What makes a great request

You don’t need a polished spec, but a few details turn a one-line ask into something we can actually act on:

Field	What to write
The problem	What you’re trying to do today and where you get stuck
Who it affects	Just you, your team, your customers, or all three
How often	Daily, weekly, or only on a specific kind of conversation
What you’ve tried	Workarounds you’ve hacked together, or other tools you’ve used
What “good” looks like	A sketch, a screenshot from another product, or a description of the ideal flow
Priority for you	Nice-to-have, would-pay-for, or blocker

We care most about the problem. If you tell us the problem, we’ll often come back with a solution that’s better than the one you originally pitched.

A good feature request looks like this

Subject: Feature Request: Per-segment escalation routing

Problem:
Right now we can route escalated tickets to a default assignee
or based on segment, but only one segment at a time. We want
to route Enterprise customers to our CSM team and free-tier
customers to a generalist queue.

Who it affects:
Our whole support team. Enterprise customers in particular
keep ending up with a generalist when they should be on the
CSM queue.

What we've tried:
We tag tickets manually after they come in, but it's a
3-step shuffle and we miss tickets when we're busy.

What good looks like:
A list of segment -> assignee rules in escalation settings,
evaluated in order. First match wins.

Priority: Would pay for.

That’s enough for us to scope, design, and ship.

What happens after you send it

We log it

Every request goes into our internal product backlog with a link back to your ticket so we can follow up with you specifically.

We respond

A real human reads it and replies. We’ll either say “we’re already building this”, “we love this and added it to the roadmap”, “here’s a workaround that might solve it today”, or “this isn’t on our roadmap yet, but we’re tracking demand”.

We build (or don't)

The ones we build get prioritized by how many customers are asking, how much pain it removes, and how well it fits where the product is going.

We tell you

When the feature ships, we email everyone who asked for it. You’ll know when it’s live.

What we say “yes” to

We’re more likely to ship something when it:

Removes work for support agents, AI or human
Makes the AI smarter with better context, knowledge, or skills
Fits cleanly into existing flows, instead of bolting on a new surface
Helps multiple teams, not just one specific use case
Is something only we can build, given our position in your support stack

What we say “no” to (or “not yet”)

We’ll usually push back when an idea:

Duplicates a tool you can already plug in via integrations
Requires us to maintain a niche feature for a single workflow forever
Adds a setting whose default would be wrong for most teams
Is a one-off customization that fits better as custom code on your side

We’ll always tell you which bucket your idea is in and why.

Roadmap and changelog

Want to see what we’re working on or what just shipped? Ask in chat or email. We don’t currently publish a public roadmap, but we share details with customers happy to.

Found a bug instead?

If something is broken (rather than missing), file a Bug Report instead.

​Where to send it

In-App Chat

Email

​What makes a great request

​A good feature request looks like this

​What happens after you send it

​What we say “yes” to

​What we say “no” to (or “not yet”)

​Roadmap and changelog

​Found a bug instead?