Settings & oversight
When to call the developer
For adminsThe few problems you can't fix in the portal, and what to have ready when you call.
Most problems can be solved without the developer. Try the guides, then the Help button in the portal, then another admin. Call the developer only for the things below.
Call the developer when
- The portal won't load for anyone.
- Every number stops replying, and Test connection for WhatsApp under Settings › Integrations fails with an access error such as "WhatsApp rejected the app's access".
- Meta shows a problem with your business account or app, such as restricted, disabled or verification.
- You changed file storage, live calls or error tracking settings. These apply only after a restart.
- A key has been lost or changed and nobody has it.
- You need a new web address, a new site, or something looks wrong with the server.
Fix it yourself first
These are not developer problems:
- One number or one assistant not replying. See Assistant not replying.
- A template rejected. See Fix a rejected template.
- Someone can't sign in. See Sign-in problems.
- Someone isn't getting alerts. See Not getting alerts.
- A broadcast that failed. See Broadcast problems.
Before you call
Have these ready:
- The page you were on.
- What you did just before.
- The exact message on screen.
- The time it happened.
- A screenshot.
- The result of Test connection for the service involved. See Church services (integrations).
Tip: Support requests from your team show where people get stuck. See Support requests.
Still stuck?
Sign in, then select Help at the bottom right of any page.
Sign in