Call Fact Table

Hello

I have a Customer Call Fact table that contains info regarding a customer call (date of call etc). The customer can initiate up to five requests , is it better to have five fields in the existing fact table to record the customer requests or have a separate table for the requests and have a relationship table between the main call record and the request records

Regards

Tim

Normally better to hold data at the lowest grain e.g. at the request - your scenario sounds similar to the order/order line case that Kimball covers extensively.
However, can you roll down all the call level attribute to the request. If not you need to think how you would handle this - aggregate the requests up to a call fact table, create a call fact table as well as a request fact table, etc.
It's your business requirements that should be driving this - how does your business understand their data (is it a call or a request) and what do they want to report on?