← BlogJune 2026 • 5 min read

Cricket Wireless Call Forwarding Not Working? 6 Fixes (2026)

Cricket Wireless runs on AT&T's network and uses identical call forwarding codes — but the most common failures are missing the # at end or omitting the +1 country code. Here are 6 fixes.

Last verified: June 2026

Quick Answer

Cricket Wireless call forwarding uses AT&T codes: *61*+1XXXXXXXXXX# (no-answer), *67*+1XXXXXXXXXX# (busy), ##002# (cancel). Most failures: (1) missing # at end, (2) missing +1, (3) use myCricket app if USSD is unreliable.

Why this carrier usually fails

Cricket uses AT&T forwarding codes, so the smallest formatting mistake can make the setup fail silently.

The practical rule is simple: fix the carrier-side formatting problem first, then test the network path, and only then move on to app or support steps. That order saves time because most forwarding issues are not Katch issues at all — they are carrier activation issues.

1. Correct code format

Cricket uses AT&T's format exactly. For no-answer forwarding, dial *61*+1[10 digits]#. For busy forwarding, use *67*+1[10 digits]#. For all calls, use *21*+1[10 digits]#. To cancel everything, dial ##002#. Both the +1 and the trailing # matter. If you leave out either one, Cricket may accept the entry but fail to apply the rule on the network side.

2. Use myCricket app

When USSD codes behave inconsistently, the app is the cleanest fallback. Open myCricket app → More → Settings → Call Forwarding → Enable and set the destination there. This is also the simplest way to confirm whether your account exposes forwarding controls at all. Cricket's official support center lives at cricketwireless.com/support, and that is the first official carrier citation you should keep open while troubleshooting.

3. Cancel and re-enable

Forwarding issues on Cricket are often stale-rule issues, not true activation failures. Dial ##002# to wipe all forwarding, wait about 15 seconds, then re-enter *61*+1[number]# for no-answer first. After that works, add the busy rule if you need it. This one-change-at-a-time method makes it much easier to spot whether the issue is the destination number, the code format, or a broader account restriction.

4. Check your Cricket plan

Cricket includes call forwarding on all normal consumer plans, including the $25/month Basic plan. If your forwarding still fails, the real question is usually not plan eligibility but whether there is some service restriction on the account. Open myCricket app → Account → Plan features and confirm voice features are active. Because Cricket plans already include forwarding, repeated failure usually points back to formatting or account provisioning rather than billing tier.

5. Disable Wi-Fi Calling

Cricket runs on AT&T infrastructure, so it inherits the same Wi-Fi Calling conflict that can block or confuse USSD forwarding requests. Go to Settings → Phone → Wi-Fi Calling → Off, set the forwarding rule, test it, then turn Wi-Fi Calling back on if you want it. This is especially worth trying when the code works on one handset but fails on another using the same Cricket SIM and same destination number.

6. Contact Cricket care

If the code format is correct and the app method still fails, contact Cricket directly. Call 1-800-274-2538 or open the chat flow inside the app and ask support to confirm that conditional call forwarding is enabled at the account level. Your second official carrier citation can be the main Cricket property at cricketwireless.com, which links back into the same official support system used for plan and feature troubleshooting.

How to Test Cricket Wireless Call Forwarding Is Working

Use a second phone and call your Cricket number. Let it ring without answering. If the setup is correct, Katch should pick up after the no-answer timer and continue the conversation with the caller. Then verify that you receive a summary text shortly afterward. If you also enabled busy forwarding, place a second test call while you are already on the line to confirm that both rules work separately.

Using Katch with Cricket Wireless

To use Katch with Cricket, set *61*+1[KATCH NUMBER]# for no-answer forwarding. Cricket uses the same codes as AT&T because it rides AT&T's network. When the carrier forwards the call, Katch answers with AI, screens the caller, and sends you a text summary so you can decide how urgent the missed call is. The full US guide is at /guides/call-forwarding-us. For carrier references, compare your setup against cricketwireless.com/support and cricketwireless.com.

Also see: AT&T troubleshootingUS carriers guideAT&T setup guide

Early Access

Get your Katch number.
Fix Jio forwarding in 60 seconds.

Free during beta. Android & iOS.

We'll text you when Katch launches.

No spam. Unsubscribe anytime. Your data is never sold.

🎉

You're on the list!

We'll text you the moment Katch launches.

Share on WhatsApp

Frequently Asked Questions

Cricket uses AT&T's codes: *61*+1[10-digit number]# for no-answer, *67*+1[number]# when busy, *21*+1[number]# for all calls. Cancel with ##002#. Always include +1 and end with #. Cricket runs on AT&T's network, so the codes are identical.
Yes. Cricket Wireless runs on AT&T's network and uses identical call forwarding USSD codes. Every fix that works for AT&T works for Cricket. The only difference is support contact: Cricket uses 1-800-274-2538, not AT&T's 611.
No. Cricket includes call forwarding on all plans at no extra charge. Calls forwarded to a Katch number use your standard Cricket voice plan minutes.
Cricket uses AT&T's infrastructure, including the same Wi-Fi Calling setup that can block USSD. Fix: disable Wi-Fi Calling in Settings → Phone → Wi-Fi Calling → Off, set forwarding, test, then re-enable it.
Yes. Set no-answer call forwarding to your Katch number with *61*+1[KATCH NUMBER]#. Katch answers missed calls with AI and texts you a summary. Setup is the same as AT&T. Full guide at /guides/call-forwarding-us.

Related guides