How to develop this data model without a circular reference

My take on this is that you may perhaps want to try using a parent-child dimension, so the model will allow for a theoretically infinited amount of levels. That way, you can connect facts to each level of the hierarchy.

Here's an example:

CREATE TABLE dimGeography (
    id
    parent_id
    geographyType
    geographyCode
    geographyName
    PRIMARY KEY (id)
);

CREATE TABLE factDemographics (
    date
    geography_id
    monthlyIncome
    workingPopulationAge
    numberOfPeople
    PRIMARY KEY (date, geography_id)
    FOREIGN KEY (geography_id) REFERENCES dimGeography (id)
);

The advantages of this approach are:

• you're free to add or remove levels as you like over time without changing the data model
• you can connect facts (demographics) to each level
• no duplicate measure columns, i.e. just one column called "number of people"
• future-proof: some countries or regions may use different types of levels - for instance, not all countries use "state".

The disadvantages that I can think of are:

• you may have to redesign your existing (?) dimension or fact table
• your BI tool may not be able to handle parent-child dimensions
• more complex SQL queries when aggregating the facts on higher levels

I haven't the slightest idea if this is the "correct" solution according to Kimball, Inmon, etc. Instead, I would urge you to see if it applies to your particular needs. ;)

Sounds like you need a proper CRM (: For the days of the week I think you have it right, have a column for each day of the week and if a day is a "no call day" you check it off. Your query would then say, "ok it's Monday who can I call?".

As far as the adhoc days (on vacation etc). You may just want to have a notes field that shows on each record on the call list. This can be reviewed before calling and modified or skipped based on the content of the note.