← All teams

ShortFreeURL for Customer Support

Short, sayable links in macros and chats, repointable when the article moves.

Support agents paste URLs all day, read them out on calls, and type them into chat windows with character limits. Long help-centre paths are hostile to all three. Short links on your own domain make them speakable, and make a documentation reorganisation something other than a disaster.

Links agents can read out loud

A short link with a readable slug can be dictated on a phone call and typed correctly first time. A deep help-centre path cannot. AI slug suggestions produce something pronounceable rather than random, and slugs stay editable if the wording proves awkward.

On your own domain, the link also reassures a customer who has been warned about clicking links from strangers.

Macros that keep working

Help centre articles get merged, renamed and moved. Every macro, saved reply and knowledge base cross-reference that points at a raw URL breaks silently at that moment. A short link layer means one bulk repoint fixes them all.

Folders group links by product area or by macro set, and folder defaults keep new links consistent with the rest.

Knowing which answers get used

Click data per link tells you which articles agents actually send and which are ignored. That is a better signal of documentation gaps than survey responses, because it reflects what agents reach for under pressure.

Automated traffic is separated out, so a link pasted into a public forum thread is not reported as agent usage.

Sensitive and time-limited shares

Support regularly needs to share something that should not stay live: a diagnostic upload page, a one-off form, a temporary workaround. Expiry by date or click count closes those automatically, and password protection gates anything that should not be forwarded freely.

Encrypted links keep a destination unreadable from our side, and referrer hiding stops a destination learning which internal system a visitor came from.

Routing customers correctly

Country and region rules send customers to their own regional support site, language edition or legal notices from a single link used in every macro. Device rules and deep links open the app where one exists.

Every rule has a fallback, so an unmatched customer still lands on the general help centre rather than an error.

Fitting the support stack

The REST API creates links from your helpdesk or knowledge base at the point an article is published, and webhooks stream click events into your own reporting. Bulk creation and CSV import cover migrating an existing library of macro links.

Roles keep the library tidy: most agents need to use links, a smaller group needs to create and edit them.

Questions

What happens when we reorganise the help centre?

Repoint the affected short links in bulk. Every macro, saved reply and past conversation that used them keeps working.

Can agents create their own links?

Yes, if their role allows it. Many teams give most agents read-only access and let a smaller group manage the library.

Can we share something that expires?

Yes, by date, by click count or by age, with a fallback destination so a late click lands somewhere useful.

Can we tell which articles agents send most?

Yes, from per-link click data grouped by folder or tag, with automated traffic excluded.

Can links route customers to their regional support site?

Yes, with country and region rules and a default for everyone else.

Give your macros a link layer that survives the next docs migration.

Start Free — no credit card

The free plan includes 1,000 links, 5 custom domains and 50,000 tracked clicks a month, free forever. Paid plans start at $4 a month when you outgrow it, and you keep everything you have built.