Each entry in the fluid field stores the content of whatever fields are defined for that entry from the set of fields assigned to the fluid field. So for each entry in your channel you might have a different set of fields defined - unlike regular fields in EE, what fields appear within a fluid field for an entry are defined when the entry is created rather than being determined by the assignment of fields to the channel.
So the only way to show the content of fluid fields is for the template to loop through the fields defined for a fluid field in an entry and on each pass through try to display what is found. So you need to put into the template code to display every possible field - the fluid field will then display the content on your page, in the order that the fluid field components have been chosen for that entry.
As a result, the template code you need display a fluid field will look a bit like this...
{fluid_field}
{subfield_1}
<html and ee template code for subfield_1>
{content}
</html and ee template code for subfield_1>
{/subfield_1}
{subfield_2}
<html and ee template code for subfield_2>
{content}
</html and ee template code for subfield_2>
{/subfield_2}
{subfield_3}
<html and ee template code for subfield_3>
{content}
</html and ee template code for subfield_3>
{/subfield_3}
... etc
{/fluid_field}
Each loop will fire one of the subfield entries, and the number of loops for an entry will equal the number of subfields defined for that entry.
For your case, one thing to be mindful of is that if you put phone number in as a possible fluid field, there is a chance that for some entries the value will not be defined (as it relies upon the phone field being selected when the entry is created) - if you are sure that all entries will have a phone number (i.e. "display each person's phone number" in your question) it might be better to use a regular field for the phone number rather than put it in the set available to a fluid field...
Hope that makes sense... :)