Company SMS, ready for the people who need it
Open a company number, find its incoming message, and copy the code or invitation link. Give the people responsible for the account access to that inbox.
From an arriving text to the next step
Select a company number to open its inbox. Messages show who sent them and when they arrived. Search by sender or text when you need to find a particular account's message. Recognized verification codes and links are available with the message, ready to copy.
Illustrative inbox message
Staging sign-in · Example sender · Just received
Your verification code is 483921. Enter it to finish signing in.
Detected code: 483921
This is an illustrative message. In your workspace, the incoming SMS and extraction result come from the actual sender. If a message's format is unfamiliar, the full text remains available to an authorized reader.
Share the inbox with its account owners
Invite teammates to the workspace, then select the sharing choice for each number. A company operations number can be restricted to its administrators while a QA number is shared with the testing team. Owners and administrators can manage restricted numbers.
The same number grant governs reading the text and accessing its recognized code. A teammate does not need another employee to forward the message when they already have the right access.
Keep context available during a handoff
A useful number label tells the next person where to look. The sender, receipt time, and retained messages help them understand an ongoing setup or troubleshoot a test. The company's number can remain in place as responsibility moves between people.
Keep the outside service's account inventory alongside this setup. Its own membership and recovery controls still determine who can sign in and administer the account. The company-access workflow shows how those two pieces fit together.
Use the inbox in development too
When a test fails, an authorized developer can inspect the same number their test runner reads. That helps separate “nothing arrived,” “the message format changed,” and “the application rejected the code.” Software reads use selected-number credentials; webhook notifications can signal receipt while the body is retrieved through authorized access.
Stored message bodies are encrypted. Default retention is 30 days from receipt. Read the security details when choosing access and retention expectations for your team.
Questions you may have
Can I search older messages?
Search covers messages still within retention. The inbox can help you find a sender or text, but it is not a permanent archive of every account event. Record long-term account ownership and recovery information in your company's normal inventory.
What if Phonekit does not recognize the code?
An authorized reader can inspect the message body. Extraction is best effort, so an unusual template may arrive successfully without a detected code. Tests should distinguish that outcome from a delivery timeout; the SDK guide shows the error cases.
Is this also a WhatsApp conversation inbox?
Phonekit receives SMS. A company may use it for an SMS step involved in account setup, subject to that service's requirements. WhatsApp conversations and outbound messaging are different capabilities from the shared SMS inbox.
Does deleting a message invalidate its code?
The sending service decides code validity and expiration. Removing the copy in Phonekit does not cancel a code elsewhere. Keep those two actions separate when investigating a failed verification.