Contact Us

Agenda 2063 spans policy communication, programme visibility, publications, data, youth engagement, and continental partnerships. Because those streams often involve different offices, this page helps visitors start from the right public-facing entry point instead of navigating disconnected channels.

It is also the right place to explain response expectations, business-hour coverage, and what information users should prepare before they submit a request. That reduces delays and helps administrators route enquiries to the correct programme or communications team.

Public users should identify whether they are asking about a publication, a programme or fellowship, a news item, performance information, a country or regional report, or a technical issue with the platform. Clear subject lines and short summaries help the team move requests faster.

When a question relates to a specific page, campaign, or document, the relevant page title and web address should be included. This allows faster internal escalation and reduces repeated clarification emails.

Media professionals may need interview coordination, press material, event clarification, or verification of official announcements. Partnership and institutional contacts may need a different routing path for strategic dialogue, referrals, or programme coordination.

This page gives administrators room to clarify how those categories are handled, what supporting documents should be attached, and whether a request should first be directed to an AU department, programme secretariat, or communications unit.

Where an issue can be handled digitally, the page should encourage users to share concise written details first. That reduces congestion, supports better recordkeeping, and makes it easier to route matters across public visibility, content, and programme teams.

When an enquiry must be escalated to an official AU office or institutional desk, the page can explain that referral process and clarify that platform administrators may not directly resolve all requests but will route them responsibly.

Administrators can use this space to explain review windows, acknowledgement practices, and the difference between content corrections, public communications, and programme-specific decisions. That helps manage expectations for users across the continent who may be engaging from different time zones and institutions.

The same CMS page can also publish temporary notices during major summits, campaigns, or programme calls so users know when response volumes are unusually high or when a request should be directed to an external official domain.