Skip to main content

Start Chat Buttons: Platform URL Guidelines (Contact Link Formats)

Use this guide to enter the correct Desktop and Mobile contact link formats for each platform in the app.

Updated over a month ago

General rules

  1. Always include the correct protocol (https://, tel:, sms://, mailto:, etc.).

  2. For phone-based links, use international format.

  3. If a platform supports prefilled messages, URL-encode the message text.

  4. Keep Desktop and Mobile links the same unless you need platform-specific behavior.


Copy-ready formats by platform

WhatsApp

Telegram

Facebook Messenger

Instagram

Facebook

TikTok

X (Twitter)

Discord

LinkedIn

Snapchat

SMS

  • Desktop/Mobile: sms://<PHONE_E164_NO_PLUS>?body=<ENCODED_TEXT>

  • Example: sms://15551234567?body=Hi%20there

  • Notes:

    • Message body is optional.

WeChat (Weixin)

  • Desktop/Mobile: weixin://dl/chat?<WECHAT_ID>

  • Example: weixin://dl/chat?mywechatid

Skype

  • Desktop/Mobile: skype:<SKYPE_USERNAME>?chat

  • Example: skype:live.mycompany?chat

Vkontakte (VK)

Slack

Email

  • Basic: mailto:<EMAIL_ADDRESS>

  • With subject/body: mailto:<EMAIL_ADDRESS>?subject=<ENCODED_SUBJECT>&body=<ENCODED_BODY>

  • Example: mailto:[email protected]?subject=Help&body=Hello

Viber

  • Public account: viber://pa?chatURI=<PUBLIC_ACCOUNT_URI>&text=<ENCODED_TEXT>

  • Phone chat: viber://chat?number=<PHONE_E164_NO_PLUS>&text=<ENCODED_TEXT>

  • Example:

    • viber://pa?chatURI=mybrand&text=Hello

    • viber://chat?number=15551234567&text=Hello

Phone

  • Desktop/Mobile: tel:+<PHONE_E164_WITH_PLUS>

  • Example: tel:+15551234567

LINE


Common mistakes to avoid

  • Missing protocol (for example, t.me/myname instead of https://t.me/myname)

  • Using spaces in phone numbers

  • Not URL-encoding message text

  • Using a profile URL that is not publicly accessible

  • Mixing username format (for example adding @ where not expected)

Quick validation checklist

Before saving:

  • Link opens directly in a new tab/device.

  • Username/ID is correct and public.

  • Message parameter (if used) is encoded.

  • Mobile link field is set (or intentionally uses the same link as Desktop).

Did this answer your question?