Accra, Ghana · Digital Operations

I make complex operations feel clear.

I turn busy digital operations—across customer channels, automation and reporting—into systems people can see, trust and improve.

Daniel Lartey standing outdoors
Daniel Lartey Digital operations · systems · AI
Current focus

Customer operations, channel reliability, automation, reporting and responsible AI adoption.

Customer operationsZendeskAutomationOperational reportingAI systemsHomeLab infrastructure

Digital operations should work for the people inside them.

I sit between business urgency and technical reality.

My work spans customer-facing digital channels, Zendesk and Sunshine Conversations workflows, chatbot operations, API troubleshooting, executive reporting, automation and AI adoption.

I care about the full operating path: what triggers the work, where the data comes from, who needs to act, what happens when it fails, and how the next person understands it without guesswork.

01

Customer experience systems

Zendesk, Sunshine Conversations, WhatsApp, web widgets, social messaging and chatbot journeys shaped around real service operations.

02

Automation and control

Reliable workflows with clear triggers, validation, approvals, retries, alerts and recovery paths instead of fragile one-off shortcuts.

03

Reporting and decisions

Operational reports and executive updates that explain movement, drivers, risks and the action that should follow.

04

Infrastructure and AI

Self-hosted services, observability and AI-assisted systems built with verification, privacy, maintainability and human judgment in the loop.

Work that connects the channel, the team and the decision.

The common thread is operational clarity. Each system has to survive the handoffs between customers, agents, data, infrastructure and leadership.

Digital customer operations

Making service channels easier to operate, not just easier to launch.

I work across digital customer-service journeys where Zendesk, Sunshine Conversations, WhatsApp, web, social messaging and internal workflows meet. The focus is practical: clearer routing, visible exceptions, useful recovery signals and reporting that reflects the actual customer experience.

  • Zendesk
  • Sunshine Conversations
  • WhatsApp
  • Chatbots
  • Service recovery
Server rack and network infrastructure

HomeGH operating platform

A real HomeLab used as an engineering and operations environment.

I run HomeGH across Proxmox, Debian systems, Zima storage, Cloudflare routes, Caddy, monitoring and self-hosted services. It is where I build, test and learn the operational habits behind reliable deployments: source control, backups, observability, recovery and honest QA.

  • Proxmox
  • VM133
  • Cloudflare
  • Caddy
  • Monitoring

Automation, reporting and AI

Turning repeated operational work into dependable systems.

I design workflows that collect the right data, validate it, surface exceptions and deliver an output people can trust. That includes scheduled reporting, n8n-style automation, API integrations and AI-assisted work with explicit review and verification gates.

  • n8n
  • APIs
  • Executive reporting
  • Agents
  • QA gates
Abstract flowing lines representing connected systems

Good systems reduce the number of heroic moments required to operate them.

  1. 01

    Start with the real operating problem.

    Understand the people, constraints, data and failure modes before choosing the technology.

  2. 02

    Design the recovery path early.

    Retries, alerts, ownership and rollback are part of the product, not cleanup work after launch.

  3. 03

    Make evidence visible.

    A deployment, report or automation is not complete until the real user path has been checked.

  4. 04

    Leave the system easier to understand.

    Clear names, source control and useful documentation keep improvements alive after the first handover.

Have an operation that keeps demanding attention?

Let’s make the next version calmer.

A useful first message explains what repeats too often, what breaks when nobody watches, and what your team needs to see sooner.

Email Daniel