How to Check Call Logs for a Specific Call in Twilio
When a Sparkforge call fails or behaves oddly, Twilio's call logs are the first stop. Open the matching Twilio sub-account, filter logs by the contact's phone number in the From or To field, and copy the Call SID for a Twilio support ticket.
If a Sparkforge call fails to connect, drops early, or behaves unexpectedly, the Twilio call log is the fastest path to root cause. It tells you which Twilio resource handled the call, the result code, and timestamps for every leg.
Find the right Twilio sub-account
- Log in at console.twilio.com.
- Top right, click Account > Subaccounts.
- Copy the Account SID for your Sparkforge location from the agency-level Twilio settings.
- Paste the SID into the Twilio search and open the matching sub-account. The orange banner at the top left confirms you're inside it.
Confirm the number is voice-capable
- Click Phone Numbers in the left panel.
- Verify the phone icon shows next to the number — that confirms voice capability.
Filter to the specific call
- Open Monitor > Logs > Calls.
- Strip formatting from the contact's phone number (no dashes, parentheses, or spaces).
- Use From to find inbound calls (the contact called your Twilio number).
- Use To to find outbound calls (your Twilio number called the contact).
- For inbound calls that forward, the first record is the routing leg.
Open the call detail
Click the hyperlinked date for the call to drill into details: SIP responses, error codes, recording links, and the full call timeline.
Escalate to Twilio support
Copy the Call SID from the detail page and open a Twilio support ticket with it. The SID lets Twilio engineers locate the exact call in their backend.
Frequently Asked Questions
How do I match a Sparkforge sub-account to its Twilio sub-account?
Should I search the From or To field?
What is a Call SID?
What if the number isn't voice-capable in Twilio?
Was this article helpful?
Thanks for the feedback.