BMLT has a feature-rich system for NA helplines called yap. It can manage volunteer lists, connect callers with NA volunteers in their areas, read and text BMLT schedule information to the caller, and read the current Just for Today.

WSZF has set up a yap server for the zone, and service bodies are welcome to use it for their helplines. There is no charge to regions or areas to use the server itself, but regions or areas will need to set up and pay for their own phone numbers using Twilio. You should be able to port existing helpline numbers to Twilio. (Other regions have reported significant savings after moving to yap from other phone systems — perhaps 1/6 their previous expenses.)

We have a zone-wide demo number that service members can use to show the system to interested service bodies and for experiments. Contact for more information. However, if your service body decides to go ahead with yap, or is even seriously considering it, you should probably start by getting your own test number from Twilio. Then you can get your number configured to your liking before going live or making a final decision.

Steps for getting yap set up in your area

  1. Set up an account on Twilio, and buy a new number. Even if you want to port your existing number, it’s good to get a test number to get the setup worked out for your area. Numbers on Twilio are cheap ($1/month for local numbers, plus any per-minute charges for using it). Twilio has free trial numbers, but it’s better to buy one — the free trial number is restricted to only call “validated” numbers, which is most inconvenient even just for testing.
  2. Get yap working for your area with your test number. (See “Configuring yap” below.)
  3. Line up volunteers willing to answer calls, and enter their numbers and times available on the yap admin website. Identify at least one of the volunteers as the person who gets notified when someone leaves a voicemail and who will return calls.
  4. To go live, port your existing number, or publish the new number on your area website and start using it. When you go live, you should probably get your Twilio account set up to automatically add more money when it drops below a certain amount (if you didn’t do this earlier).

Here are directions for porting existing numbers to Twilio:

Configuring yap

There are two different things you need to configure: the settings on Twilio, and the settings on the yap admin panel.

Settings on Twilio

Log into your Twilio account to set these. The following two screenshots show the webhooks to provide in the Twilio dashboard for using the zone’s yap server. These are for Seattle Area (whose ID is 3 in the zonal server). Substitute the ID for your region or area for the 3 in the URLs. To find this ID, go to, then pick “get service bodies” and click on the “response URL”. The ID will be the number in the first column corresponding to the area or region you want. The webhooks are also shown as text after the screenshot to make it easier to copy and paste them into your Twilio dashboard.

Setting up the voice webhooks for yap on the Twilio dashboard
The SMS webhook

Settings on the yap admin panel

Log into the yap admin panel at, select your service body, then “configure”. Some items that you need to override are twilio_account_sid and twilio_auth_token (get these from the Twilio dashboard), and the title (which gets read out to the caller).

Yap provides a large number of other settings that can be configured as well. These generally have reasonable default values, so you can just leave them alone if you want (particularly when getting started). Two that are overridden from the factory defaults in the zone’s configuration are:

You can further override these in your region or area configuration. If you set $sms_summary_page = false, the default is to send 5 separate text messages with the top 5 meetings. Instead you can set $sms_combine = true to combine them into one text, or set $sms_ask = true to ask first before sending these texts.

Regional yap servers

In addition to the zonal yap server, some regions in the zone have their own yap servers. It’s fine to continue using those indefinitely, even if the region moves its BMLT data to the zonal server. Alternately, existing yap installations can be re-directed to use the zonal server once the region’s data is moved over, although some work will be needed to fix service body IDs and similar things. Here is a blog post with some suggestions for migrating a regional yap server into a zonal one: