● SIP/2.0 200 OK  |  RTP: flowing  |  New guides added weekly

Contact

Contact VoIP Cost Guide

By the VoIP Cost Guide Editorial Team  |  Last updated: October 2026

Questions about a guide, a correction to suggest, or a topic you would like covered in a future weekly update? Use the form below.

Before you write: three things that help

For troubleshooting questions, the most useful messages name the symptom precisely (one-way audio is a different fault from no audio), the setup (hosted service or on-premise system, phone models, and any recent network change), and what the failure looks like in a capture if you have one — the SIP response code or the point in the call where things break. Our troubleshooting method guide shows the information that pins a fault down fastest. Please note we can point you to the right guide and explain concepts, but we cannot log into, configure or take responsibility for your phone system.

For cost questions, tell us the seat count, the country you are buying in, and which line items a quote contains. The worked budgets in the costs pillar answer most pricing questions directly; the total cost checklist is the fastest way to audit a quote for missing lines.

For corrections, a link to the page and the figure or statement you believe is wrong — ideally with the source you are working from — gets the fastest review. Pricing models and fee schedules change, and reader corrections are a real part of how this site stays accurate.

What happens after you send the form

Messages land with the editorial team — the same people who write and revise the guides. A correction with a source is checked against the primary material (the standard, the fee schedule, the provider document) and, if it holds, the guide is updated and its last-updated date moves; you will get a short reply saying what changed. A good question that no guide answers yet joins the weekly topic queue, and the strongest reader questions regularly become the next published guides — the weekly cadence described on the homepage exists largely to work through them. A question a published guide already answers in full will usually receive a reply pointing to that guide, so the team's time stays available for new research.

What this form is not for

Three honest limits. First, emergencies: if your phone system carries emergency calls and something about its 911 behavior is wrong, contact your provider's support line immediately — a web form read on weekdays is not an emergency channel. Second, account support: we are not your provider and cannot see, change or escalate your account, your bill or your service; only your provider can do those things, though our guides can help you talk to them precisely. Third, sales and pitches: the site carries no sponsored content and sells no placements, so proposals of that kind are not answered. Everything else — questions, corrections, topic suggestions, disagreements with a guide's conclusion argued from evidence — is welcome and read.

Send a message

Messages are read by the editorial team and answered in the order received, normally within two business days; a reply is not guaranteed for questions a published guide already answers in full, and during high-volume periods corrections from readers take priority over general questions because they improve the guides for every reader who follows.

Your details are used only to reply — see the privacy policy. Never send passwords, account credentials or payment details through this form.