Set up shared SMS access for a company account
Use this worksheet to move a company account from “ask the person with the phone” to a repeatable team workflow. Finish with a login that the next responsible teammate can complete.
Fill in one account record
Choose an account the team already uses. Record enough context that someone can find its number and administer the account later.
| Field | Example entry / what to record |
|---|---|
| Service and account | Product workspace and its account identifier |
| Responsible team | Product operations |
| Service administrators | Current owner and backup administrator |
| Number label | Product operations |
| Reason for SMS | Sign-in, account setup or invitation |
| Inbox readers | People who perform that step |
| Recovery location | Reference to the approved credential store |
| Last working check | Date, step tested and responsible person |
Scroll horizontally to see all columns.
The number supports the service's access flow. Use the service's own team membership and delegated roles so each person also has the right permissions after sign-in.
Connect and check the intended step
- Assign a company number with a recognizable label.
- Follow the service's supported account-number setup or change process.
- Request the verification message for the actual step you need.
- Retrieve it in Phonekit and finish the step in that service.
- Record the date and outcome in the account inventory.
If a personal number is being replaced, keep authorized access available while completing the change. Changing a service's destination number is different from transferring that existing number between phone providers.
Let a second teammate complete the workflow
Choose number access for the people responsible for the account. A restricted operations inbox and a broadly shared QA inbox can coexist in the same workspace. In Phonekit, owners and administrators retain access to restricted numbers.
Ask another authorized teammate to repeat the intended login or setup step using their service role and shared inbox access. This reveals missing service membership, unclear labels or recovery dependencies before an urgent handoff.
Your completed setup record
Account: identified · Owner and backup: assigned · Number: labeled · Delivery step: checked · Second teammate: successful · Recovery: located
Keep the record useful after setup
Review it when account responsibilities change. Update the service administrators, inbox readers and software credentials independently. Keep recovery material in the company's approved credential store; reference its location in this worksheet.
The inbox's default retention is 30 days from receipt, so the account record should hold durable ownership information rather than depend on finding the original setup text months later.
Questions you may have
Who should have inbox access?
Start with the people who actually administer or use the account. Sharing applies to the number’s inbox, so choose separate numbers when unrelated accounts need different readers. Workspace owners and administrators retain access to restricted numbers.
Can the shared inbox replace service team roles?
The inbox supplies the SMS step. The outside service determines membership, permissions and active sessions. Configure both so retrieving a message and administering the account have clear owners.
What if a service refuses the number?
Record which step refused it, the country and the number requirement. Use the number-selection worksheet and confirm an available option with us before changing a working company account.