Contact
Contact TremorWatch for questions about risk briefings or the data platform.
Contact TremorWatch
For questions about TremorWatch Blog, weekly risk briefings, data-source methodology, or the TremorWatch platform, contact the Volt AI team through the main TremorWatch site. The blog is designed as the public editorial layer, while the platform provides deeper access to risk signals, source context, and operational monitoring workflows.
Use the weekly briefing request form if you want to receive or follow up on the supply-chain risk briefing. Use the live dashboard link if you are evaluating the data platform, need a product conversation, or want to understand how TremorWatch can support procurement, logistics, risk, or executive reporting workflows.
What to include
For methodology questions, include the page or briefing you are asking about and the specific source, category, or risk-score concept that needs clarification. For platform or demo questions, include your organization, use case, regions or commodities of interest, and whether you are focused on sourcing, logistics, continuity planning, or executive monitoring.
For privacy, advertising, or data-use questions, include the page involved and the type of request you are making. If you are asking about a submitted briefing email, include the email address used for the request so the team can locate the record. Do not send confidential supplier lists or sensitive shipment data through a public contact channel unless a secure workflow has been arranged.
Response expectations
TremorWatch Blog is not an emergency response service and does not provide real-time operational instructions. Public risk content should be treated as a starting point for review. If you are dealing with an active safety, security, legal, or logistics emergency, use the appropriate official and professional channels first.
The team prioritizes requests related to weekly briefings, data methodology, platform evaluation, and corrections to public content. If a page appears outdated or unclear, include the URL and what you believe needs correction so it can be reviewed efficiently.
For corrections, the most helpful message explains the specific claim, the reason it may be wrong, and any public source that supports the correction. For commercial questions, the most helpful message explains the workflow you are trying to support and the decisions the team needs to make. That context helps TremorWatch respond with the right level of detail instead of a generic answer.
Examples include monitoring suppliers near wildfire regions, reviewing logistics exposure around unrest, understanding a risk score, requesting a demo for a sourcing team, or asking how weekly briefings are assembled. Clear context helps route the message to the right person and reduces back-and-forth.