Contact
Send us a message
Story tips, corrections, reader questions or collaboration enquiries — our desk reads everything.
How to reach the Pulsecspark editorial desk
Whether you've spotted an error in one of our articles, have a dataset you think deserves scrutiny, or want to collaborate on a research or education project, we want to hear from you. Fill in the form below and a team member will respond within two working days. For urgent corrections, please mark your subject line clearly and we will prioritise. We receive a high volume of PR outreach — if you're pitching a commercial story, please state that upfront so we can route it correctly. Our office in Thika is staffed Monday to Friday, 08:00–17:00, and on Saturday mornings until 13:00.
Our details
You can also reach us directly by phone or email during office hours.
- Address
Kenyatta Avenue, Thika 01000, Kenya - Phone
+254 712 345678 - Email
info@pulsecspark.com - Hours
Mon–Fri 08:00–17:00, Sat 09:00–13:00
Common questions about contacting us
Can I submit a story tip anonymously?
Yes. You don't need to give your name or affiliation. If you want a response, include a contact method — but tips without contact details are read and considered on their own merits.
Do you accept contributed articles or op-eds?
We don't publish opinion columns or contributed essays. All Pulsecspark content is reported and written by our editorial team to maintain consistent standards and editorial independence.
How do I report a factual error?
Email info@pulsecspark.com with the article title, the specific claim and the correct figure or fact with its source. We investigate all corrections and publish a note on the article if an error is confirmed.
Are you open to research partnerships?
We have worked with Kenyan universities on data literacy projects before and are open to discussing collaborations with academic or civil-society organisations, provided editorial independence is maintained throughout.
Not ready to write? Browse our work first.
Start with our latest economics explainers and see how we approach the data.
Read the articles