Fact table design based on sales appointments

I am looking for advice on fact table design.
I have 2 base tables. Sales Appointments and Sales Proposals.
An Appointment may have 1 or many or no Sales Proposals.
We wish to analyze this data by appts and proposal. So my most granular fact is the proposal if it exist.
Table examples are abreviated.
ApptTable:
ApptID, Date, Type, Customer data...
Proposal Table:
ApptID, Date, Type, SubType, Amt,OutCome

Is it "ok" to have a wide table with appt data, customer data and proposal data would be null?
If a single table the appt data would be repeated many times, using Distinct counts handles this issue.

Comments and advice are appreciated.